Which versions of ripshakti1 are malicious?

The following npm versions of ripshakti1 are flagged malicious: 81.0.0. Treat any of these as compromised.

How do I remediate ripshakti1 if I installed it?

ripshakti1 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 ripshakti1 — how do I know if it already compromised me?

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

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

Malicious package

ripshakti1npm

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

Malicious code in ripshakti1 (npm)

MAL-2026-6674

Immediate action

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

npm uninstall ripshakti1

What this malware does

package.json declares a preinstall lifecycle hook (node index.js) that auto-executes on npm install. index.js queries the AWS EC2 instance metadata service (IMDSv2 and v1) at 169.254.169.254 for IAM role credentials, instance identity, user-data, and network/host metadata, queries the ECS task credentials endpoint at 169.254.170.2, and filters process.env for keys matching secret-shaped patterns (key, secret, token, pass, auth, cred, api, aws, database, db_, mongo, redis, s3, sqs, sns, lambda, role). Each payload is base64-encoded and exfiltrated via HTTPS GET to the attacker-controlled Burp Collaborator subdomain a2de2lw03amqkgbex432znqb72du1kp9.oastify.com. This auto-fires on every install, including transitive installs and CI runners.

The OpenSSF Package Analysis project identified 'ripshakti1' @ 81.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

81.0.0

Indicators of compromise (SHA-256)

99eb23386bdacc07b7fb8da75fb4a04c93d247e322b4aec2685b1270056683bf

764edbf390c427ef99a9d9164034b966fbac251f00240bbb219825c0c92422a6

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 ripshakti1 (version 81.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ripshakti1 across your stack and pipelines.
If you installed it — respond
ripshakti1 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 ripshakti1 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 ripshakti1 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. ripshakti1 on npm has been identified as a malicious package (version 81.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007817

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ripshakti1-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