Which versions of wds-icons are malicious?

The following npm versions of wds-icons are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate wds-icons if I installed it?

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

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

Yes — wds-icons is associated with the GHSA-jhm5-cg5j-fj77 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 wds-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 wds-icons (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wds-icons across your stack and pipelines.

Malicious package

wds-iconsnpm

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

MAL-2025-191494

Immediate action

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

npm uninstall wds-icons

What this malware does

The package wds-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.

The OpenSSF Package Analysis project identified 'wds-icons' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

fb173468877c6a6ec8dd97252a49a2e007320448f178d14dafe5fd5ceaeddac2

827b1d3e49cfad3ca5aa4eeb1a7afedc234ed734e13948ba28b0e3b3b71180cc

24d19b105cd9931a78806b2c2f9a30d8ef982b16e1ed4620c185a75dbbbf610d

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

Campaign

GHSA-jhm5-cg5j-fj77

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks wds-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