Which versions of @agilent/awf-styles are malicious?

The following npm versions of @agilent/awf-styles are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate @agilent/awf-styles if I installed it?

Remove @agilent/awf-styles from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @agilent/awf-styles — how do I know if it already compromised me?

If @agilent/awf-styles was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @agilent/awf-styles part of a known attack campaign?

Yes — @agilent/awf-styles is associated with the RLMA-2024-10377, RLUA-2026-05798 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @agilent/awf-styles across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @agilent/awf-styles (version 99.9.9).

Malicious package

@agilent/awf-stylesnpm

Advisory published Dec 8, 2024Updated Sep 1, 2026

@agilent/awf-styles is a confirmed malicious npm package (MAL-2024-11253) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @agilent/awf-styles (npm)

MAL-2024-11253

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @agilent/awf-styles

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

f5fcbdf19b9ec13309e9ab93a7c1d619c37db2e44240c832d61427aeb1ae3605

2f21baa3b4628679a4e5948ec20106044a9b4f57572ff1d7409312cd09e7f648

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @agilent/awf-styles (version 99.9.9).
If you installed it — respond
Remove @agilent/awf-styles from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @agilent/awf-styles was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @agilent/awf-styles on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-10377RLUA-2026-05798

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @agilent/awf-styles-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database