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?

stripe-cli-init-plugin is a typosquat — you almost certainly intended a legitimately-named package. Remove stripe-cli-init-plugin, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed stripe-cli-init-plugin — how do I know if it already compromised me?

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

How do I find stripe-cli-init-plugin 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 stripe-cli-init-plugin (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stripe-cli-init-plugin across your stack and pipelines.

Malicious package

stripe-cli-init-pluginnpm

stripe-cli-init-plugin is a confirmed malicious npm package (MAL-2026-5899) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stripe-cli-init-plugin (npm)

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

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stripe-cli-init-plugin (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stripe-cli-init-plugin across your stack and pipelines.
If you installed it — respond
stripe-cli-init-plugin is a typosquat — you almost certainly intended a legitimately-named package. Remove stripe-cli-init-plugin, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If stripe-cli-init-plugin 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 stripe-cli-init-plugin 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. 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

Detect & block this

O3 blocks stripe-cli-init-plugin-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