Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

xo-wallet-componentsnpm

xo-wallet-components is a confirmed malicious npm package (MAL-2025-47365) that steals credentials and exfiltrates sensitive data (malicious version 99.0.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xo-wallet-components (npm)

MAL-2025-47365
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall xo-wallet-components

What this malware does

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.0.99

Indicators of compromise (SHA-256)

94fd297d5bd2cbf348e88599e570974a4fc9f65f7bf3cdda6bf6a69e8dc8dd44
499f4a649ca193169bf4a2ba26aae24ca6bbc0ba5c6ae4fc387b7c5d7c4ce344
d982add4159f71d067a57ba5a1ca0e317007aef90034d526057c34663470af67
c4716963b473c2b5b488e9702ccc3a85c06316b75d98b941923b801a8de72a0e
1291d92a9e2697fd819562d1cd124b5b1b7eb459f85d3154e6546099e0392473

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    xo-wallet-components is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If xo-wallet-components 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.

  4. How O3 protects you

    O3 blocks xo-wallet-components 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. xo-wallet-components on npm has been identified as a malicious package (version 99.0.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-367p-qqv8-8hq8RLMA-2025-05203RLUA-2026-01656

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks xo-wallet-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

xo-wallet-components (npm) malicious package — MAL-2025-47365 | O3 Security