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?

Remove @vibelet/cli 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 activity or persistence.

I already installed @vibelet/cli — how do I know if it already compromised me?

If @vibelet/cli 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 @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?

Search your lockfiles and build artifacts for @vibelet/cli (version 1.2.154).

Malicious package

@vibelet/clinpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

@vibelet/cli is a confirmed malicious npm package (MAL-2026-10720) that executes malicious code on install (malicious version 1.2.154). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @vibelet/cli (npm)

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

Malicious package

Find it
Search your lockfiles and build artifacts for @vibelet/cli (version 1.2.154).
If you installed it — respond
Remove @vibelet/cli 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 activity or persistence.
Did it already run?
If @vibelet/cli 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. @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 malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database