Which versions of icons.generated are malicious?

The following npm versions of icons.generated are flagged malicious: 99.9.13. Treat any of these as compromised.

How do I remediate icons.generated if I installed it?

Remove icons.generated 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 icons.generated — how do I know if it already compromised me?

If icons.generated 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 icons.generated part of a known attack campaign?

Yes — icons.generated is associated with the RLMA-2026-05112, RLUA-2026-06279 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 icons.generated across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for icons.generated (version 99.9.13).

Malicious package

icons.generatednpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

icons.generated is a confirmed malicious npm package (MAL-2026-7298) that executes malicious code on install (malicious version 99.9.13). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in icons.generated (npm)

MAL-2026-7298

Immediate action

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

npm uninstall icons.generated

Malicious versions

1 flagged

99.9.13

Indicators of compromise (SHA-256)

b6a5490e2bb6eaeeeb1b03496a22692403ae35ea0ca2990d01c872a8269afe00

38389ea0624e1c78e08c58f22bafe219801445d258d18b3a89ce2ce2b96e90c4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for icons.generated (version 99.9.13).
If you installed it — respond
Remove icons.generated 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 icons.generated 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. icons.generated on npm has been identified as a malicious package (version 99.9.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05112RLUA-2026-06279

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks icons.generated-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