What does the sarumaan_a malware do?

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.

Which versions of sarumaan_a are malicious?

The following npm versions of sarumaan_a are flagged malicious: 1.1.1, 1.1.3. Treat any of these as compromised.

How do I remediate sarumaan_a if I installed it?

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.

I already installed sarumaan_a — how do I know if it already compromised me?

If sarumaan_a was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find sarumaan_a across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sarumaan_a (2 malicious versions).

Malicious package

sarumaan_anpm

Advisory published Dec 18, 2025Updated Dec 22, 2025

sarumaan_a is a confirmed malicious npm package (MAL-2025-192606) that executes malicious code on install (malicious versions 1.1.1, 1.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sarumaan_a (npm)

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

Find it
Search your lockfiles and build artifacts for sarumaan_a (2 malicious versions).
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.
Did it already run?
If sarumaan_a was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database