Which versions of @agilent/web-icons are malicious?

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

How do I remediate @agilent/web-icons if I installed it?

Remove @agilent/web-icons 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/web-icons — how do I know if it already compromised me?

If @agilent/web-icons 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/web-icons part of a known attack campaign?

Yes — @agilent/web-icons is associated with the RLMA-2024-10379, RLUA-2026-05800 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/web-icons across my projects, lockfiles, and CI pipelines?

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

Malicious package

@agilent/web-iconsnpm

Advisory published Dec 8, 2024Updated Sep 1, 2026

@agilent/web-icons is a confirmed malicious npm package (MAL-2024-11255) 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/web-icons (npm)

MAL-2024-11255

Immediate action

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

npm uninstall @agilent/web-icons

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

36c44c51a5916e8d09b1f7f0fd02e0bd294cacbd2f042e96d23030f342c697f6

0ef240a0d8816ce68e34b63167cb389db857bb99c2989f5b57dd2545f1964891

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @agilent/web-icons (version 99.9.9).
If you installed it — respond
Remove @agilent/web-icons 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/web-icons 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/web-icons 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-10379RLUA-2026-05800

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @agilent/web-icons-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