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

smart-utils-alicenpm

Malicious code in smart-utils-alice (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192595
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall smart-utils-alice

What this malware does

The package smart-utils-alice 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

6 flagged
999.0.1999.0.2999.0.3999.0.99999.0.100999.0.101

Indicators of compromise (SHA-256)

6732541d5454e88aef92a4c52a387287edbc24420d0dd35377e1d9e41a332fd7
2de5b916487c66ac49dea93a8859097db125ab6c1b8ea18a72bd3f72cdcfaff6
2bc4df2d0bd45ac6a8a13e349a2aae5f2663e126cb8273e0b892c4f41770cdd2
c79785757e4c56b88b3680a5732f3002290f1f0af69f31eaa2b62bf6828e515e

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove smart-utils-alice 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.

  3. Did it already run?

    If smart-utils-alice 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 smart-utils-alice 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. smart-utils-alice on npm has been identified as a malicious package (versions 999.0.1, 999.0.2, 999.0.3, 999.0.99, 999.0.100, 999.0.101 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6fwq-962w-p65hRLMA-2025-06484RLUA-2026-01579

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks smart-utils-alice-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.

smart-utils-alice (npm) malicious package — MAL-2025-192595 | O3 Security