Which versions of @vibelet/cli are malicious?

The following npm versions of @vibelet/cli are flagged malicious: 1.2.154. Treat any of these as compromised.

How do I remediate @vibelet/cli if I installed it?

@vibelet/cli 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 @vibelet/cli — how do I know if it already compromised me?

If @vibelet/cli 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 @vibelet/cli part of a known attack campaign?

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

Malicious package

@vibelet/clinpm

Malicious code in @vibelet/cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10720

Immediate action

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

npm uninstall @vibelet/cli

What this malware does

The @vibelet/cli package ships a daemon bundle (dist/index.cjs, invoked by the vibelet bin and by vibelet start/restart/reset) that starts an HTTP+WebSocket server, spawns an interactive PTY running process.env.SHELL via node-pty, and pipes network-received 'input' and 'resize' messages into that PTY. By default the CLI provisions a public Cloudflare tunnel (trycloudflare.com, using the bundled cloudflared and ws dependencies) that fronts this endpoint, so any remote party that pairs with the daemon (or obtains the tunnel URL together with the short-lived pair token) can execute arbitrary commands in a full interactive shell on the installer's host. The daemon bundle is packed with obfuscator.io-style transforms (string-array dispatcher _0x9d44, hex-encoded identifiers, control-flow flattening) rather than ordinary minification, which obscures the network-to-PTY path.

Malicious versions

1 flagged

1.2.154

Indicators of compromise (SHA-256)

3f3dc6503f9f63413994c6d0b2e19f22ebcf17f5e7ba9f713ce26ecf69c92c6c

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

Campaign

IN-MAL-2026-010734

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @vibelet/cli-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