Which versions of @ikeacnalan/icons are malicious?

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

How do I remediate @ikeacnalan/icons if I installed it?

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

If @ikeacnalan/icons was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @ikeacnalan/icons part of a known attack campaign?

Yes — @ikeacnalan/icons is associated with the GHSA-4prp-gwjj-hvcx, RLMA-2026-01017 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 @ikeacnalan/icons across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ikeacnalan/icons (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ikeacnalan/icons across your stack and pipelines.

Malicious package

@ikeacnalan/iconsnpm

Malicious code in @ikeacnalan/icons (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-676

Immediate action

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

npm uninstall @ikeacnalan/icons

What this malware does

The package @ikeacnalan/icons was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

ffce36957053215e07b62bff611f41214d93c6ea09b50ac90e9d28fe7d22e3ba

69aa8245ea172b28e43591f47b972fc5e5901c90a4154f6b5962f7a9a3a2e844

3ca16593a98e05c20bd988ba544c9fefc4ed65cf10618365e68998d6dff524bb

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ikeacnalan/icons (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ikeacnalan/icons across your stack and pipelines.
If you installed it — respond
Remove @ikeacnalan/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 @ikeacnalan/icons was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @ikeacnalan/icons before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @ikeacnalan/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

GHSA-4prp-gwjj-hvcxRLMA-2026-01017

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @ikeacnalan/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