Which versions of el-icon are malicious?

The following npm versions of el-icon are flagged malicious: 1.1.9, 1.2.1, 1.2.2. Treat any of these as compromised.

How do I remediate el-icon if I installed it?

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

If el-icon 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 el-icon part of a known attack campaign?

Yes — el-icon is associated with the GHSA-gfm3-3p4f-m57w, RLMA-2026-01751, RLUA-2026-01941 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 el-icon 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 el-icon (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging el-icon across your stack and pipelines.

Malicious package

el-iconnpm

Malicious code in el-icon (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1947

Immediate action

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

npm uninstall el-icon

What this malware does

The package el-icon 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

3 flagged

1.1.91.2.11.2.2

Indicators of compromise (SHA-256)

a5783aeff6b8639c7ecb526c39e297c96949bead58c8e1aabf1be7417d75e696

2a3c49d25d54c1bd3e1e5ba1ab4996329e8244ba30c1639f977985930fafd91f

ee1fcaced2ca50f8bb35a2081dbc6b8de03c27384b1b6d58feb5f095ad542893

e63b8428e4ed320388be0b7bc9054dc7edf00064c26b26124387fc5302f3ce33

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 el-icon (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging el-icon across your stack and pipelines.
If you installed it — respond
Remove el-icon 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 el-icon 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 el-icon 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. el-icon on npm has been identified as a malicious package (versions 1.1.9, 1.2.1, 1.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gfm3-3p4f-m57wRLMA-2026-01751RLUA-2026-01941

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks el-icon-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