Which versions of @wb-drive/icons are malicious?

The following npm versions of @wb-drive/icons are flagged malicious: 2.4.9. Treat any of these as compromised.

How do I remediate @wb-drive/icons if I installed it?

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

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

Yes — @wb-drive/icons is associated with the GHSA-pp9p-p4m6-rh8x, RLMA-2025-06051 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 @wb-drive/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 @wb-drive/icons (version 2.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wb-drive/icons across your stack and pipelines.

Malicious package

@wb-drive/iconsnpm

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

MAL-2025-191951

Immediate action

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

npm uninstall @wb-drive/icons

What this malware does

The package @wb-drive/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

2.4.9

Indicators of compromise (SHA-256)

b963cc99aeb3b018cc92bf91e1468db917afc1b925c97a52799b987f8d46bc94

01c73b9d74d08599396bf602ee611ff710e750f219277fd8814584c4406eef80

64f2489fe3914afb5df5d5dfda213cf6047da00cdd76418d1d21e51f233b94f0

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

Campaign

GHSA-pp9p-p4m6-rh8xRLMA-2025-06051

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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