Which versions of stripedev are malicious?

The following npm versions of stripedev are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate stripedev if I installed it?

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

If stripedev 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.

Is stripedev part of a known attack campaign?

Yes — stripedev is associated with the IN-MAL-2026-010513 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 stripedev across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stripedev (version 1.0.0).

Malicious package

stripedevnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

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

Malicious code in stripedev (npm)

MAL-2026-10592

Immediate action

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

npm uninstall stripedev

What this malware does

package.json declares postinstall: node.init.js, which runs automatically on npm install. The script enumerates ~60 credential and CI-token environment variables (including NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, STRIPE_, DOCKER_, HEROKU_*, GCP, and Azure keys), reads ~/.npmrc, ~/.env*, ~/config.json, and ~/credentials.json, and walks ~/.config for files containing token/cred/secret. Host identifiers (os.hostname(), os.platform(), process.cwd(), pid) are collected alongside the secrets. All collected data is HTTPS-POSTed to a hardcoded webhook.cool endpoint (webhook.cool/at/tender-deer-80/hG-DWynJKenViD9XWI5Mf8CulD0I9G2s). The package has no legitimate functionality corresponding to this behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e8b1bd48eb1fe3b563d9950f59df7fcfe699d0f1b51820c47b721f59ee74af34

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for stripedev (version 1.0.0).
If you installed it — respond
stripedev 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 stripedev 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. stripedev on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010513

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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