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

sarumaan_anpm

Malicious code in sarumaan_a (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192606
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sarumaan_a

What this malware does

The package sarumaan_a was found to contain malicious code.

The OpenSSF Package Analysis project identified 'sarumaan_a' @ 1.1.1 (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

2 flagged
1.1.11.1.3

Indicators of compromise (SHA-256)

936358da4e0584be78e54ed71a2f77b06fcde56b7a007877e52646da270b7fea
e590ffec4a066c881351a8bc82b4bc1330751b9a879ec12b5dbb50d45ea5f37f
44f1d6e1dae6e429d4b5cffe6573928f3e9f5f816a3676747d786bce3c32d175

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 sarumaan_a (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sarumaan_a across your stack and pipelines.

  2. If you installed it — respond

    Remove sarumaan_a 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 sarumaan_a 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 sarumaan_a 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. sarumaan_a on npm has been identified as a malicious package (versions 1.1.1, 1.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks sarumaan_a-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.

sarumaan_a (npm) malicious package — MAL-2025-192606 | O3 Security