Which versions of ripshakti are malicious?

The following npm versions of ripshakti are flagged malicious: 80.0.0. Treat any of these as compromised.

How do I remediate ripshakti if I installed it?

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

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

If ripshakti 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 ripshakti part of a known attack campaign?

Yes — ripshakti is associated with the IN-MAL-2026-007816 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 ripshakti 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 ripshakti (version 80.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ripshakti across your stack and pipelines.

Malicious package

ripshaktinpm

ripshakti is a confirmed malicious npm package (MAL-2026-6701) that steals credentials and exfiltrates sensitive data (malicious version 80.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ripshakti (npm)

MAL-2026-6701

Immediate action

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

npm uninstall ripshakti

What this malware does

The package's preinstall lifecycle hook (scripts.preinstall = "node index.js") auto-executes index.js on npm install. The script queries the AWS instance metadata service at 169.254.169.254 for IAM security credentials, instance identity, user-data and network metadata, reads ECS container credentials endpoints, and enumerates process.env filtering for keys matching /key|secret|token|pass|auth|cred|api|aws|database|db_|mongo|redis|s3|sqs|sns|lambda|role/i. Collected data is base64-encoded and POSTed to a hardcoded out-of-band collector at https://9x7dxkrzy9hpff6ds3y1umla218swik7.oastify.com. Any developer, CI runner, or EC2/ECS host that runs npm install for this package has its cloud IAM role credentials and environment secrets exfiltrated to an attacker-controlled endpoint.

Malicious versions

1 flagged

80.0.0

Indicators of compromise (SHA-256)

aa7ce8c4b0c7a25d70f9043d4208694cdef5ad174aa493ee9e9097ea6693a668

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ripshakti (version 80.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ripshakti across your stack and pipelines.
If you installed it — respond
ripshakti 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.
Did it already run?
If ripshakti 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 ripshakti 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. ripshakti on npm has been identified as a malicious package (version 80.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007816

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database