Which versions of stripe-cli-init-plugin are malicious?

The following npm versions of stripe-cli-init-plugin are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate stripe-cli-init-plugin if I installed it?

Remove stripe-cli-init-plugin 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is stripe-cli-init-plugin part of a known attack campaign?

Yes — stripe-cli-init-plugin is associated with the IN-MAL-2026-006754 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect stripe-cli-init-plugin in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking stripe-cli-init-plugin and packages like it before any post-install script runs.

Malicious package

stripe-cli-init-pluginnpm

Malicious code in stripe-cli-init-plugin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5899

Immediate action

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

npm uninstall stripe-cli-init-plugin

What this malware does

Package name 'stripe-cli-init-plugin' impersonates the Stripe CLI ecosystem and ships a bin script (bin/run.js) that, when invoked via npx stripe-cli-init-plugin or as the installed CLI, POSTs the installer's project directory basename and a timestamp to a hardcoded remote URL (https://deepbounty.dd06-dev.fr/cb/10306845-ff21-4176-8574-95dd4917bc45). The package self-describes as a 'Security PoC for Bug Bounty' but is published to the public npm registry under a name designed to be reached via typo or autocomplete confusion against the legitimate Stripe CLI tooling, and provides no advertised functionality — its only effect on the installer is to confirm execution and leak the CWD basename to the author's server. The combination of name-confusion targeting a top-tier brand plus a silent phone-home to an attacker-controlled endpoint constitutes a supply-chain attack regardless of the author's stated intent.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

05bd1dbc9732ef80aca27acad964c041b74e646e26cf4947ad34807c41d2c4a8

Frequently asked questions

No. stripe-cli-init-plugin 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-006754

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection