Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@dervix/wsnpm

@dervix/ws is a confirmed malicious npm package (MAL-2026-6496) that steals credentials and exfiltrates sensitive data (malicious versions 8.21.0, 8.21.1, 8.21.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @dervix/ws (npm)

MAL-2026-6496
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @dervix/ws

What this malware does

Package @dervix/ws impersonates the popular ws WebSocket library — package.json copies the legitimate ws project's homepage (https://github.com/websockets/ws), repository, and author metadata while publishing under an unrelated scope. lib/websocket.js appends ~130KB of heavily obfuscated code after the genuine socketOnError function; this payload executes at require() time via index.js. On import the payload (1) re-spawns the current Node process detached with stdio:'ignore' and windowsHide:true, gated by an obfuscated marker env var so the parent returns cleanly while a daemonized child continues; (2) constructs an AES-256 key by XOR-combining four hardcoded hex Buffers; (3) issues an HTTPS GET (following 3xx redirects) to an encrypted-in-source URL, streams the response to a file under os.tmpdir(), and decrypts it via createDecipheriv; (4) fs.chmodSync(path, 0o755) and child_process.spawn(path,...) with detached:true then unref()s it. Dynamic import('child_process') / import('path') is used to defeat static require audits, and an inspector.url() check short-circuits execution when a debugger is attached. There is no signature verification, no version pinning, and the destination URL is RC4-decoded at runtime so it cannot be inspected statically. Combined with the cloned ws metadata, this is a deliberate typosquat dropper that lands and executes attacker-controlled binary code on any machine that installs and imports the package.

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

6 flagged
8.21.08.21.18.21.38.21.48.21.58.21.7

Indicators of compromise (SHA-256)

09575a7546e1b46b4042a1d2437450ba5b76d3bee8993eba8c0226fe994939f7
79b9ab7431b1a6a1250c089e2ea33f54ad92313f587fbd2aabc020c12be55f69
4e2a63fe658b5c4b3bec127c4048a7df778ce6fa0a09b8e25780bc456bccd734
b0c3046401ca7c230339c585db9d1e925c670b5739209048b6d29f88b14ddc01
8ad9f3b4f5a4693c278bb3666cd3e36adaec81bfabc3ed2f685e7ef34016bc72
e59d5453dbbab9e2e4d63d7ee6590d6f0dbda982bf398a458332f28f0265ea7c
1919c272973214f8b3e7877a22f9c6eb9663b34016a84b7b3535ac03a04a2e5d

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @dervix/ws (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @dervix/ws across your stack and pipelines.

  2. If you installed it — respond

    @dervix/ws 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.

  3. Did it already run?

    If @dervix/ws 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.

  4. How O3 protects you

    O3 blocks @dervix/ws 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. @dervix/ws on npm has been identified as a malicious package (versions 8.21.0, 8.21.1, 8.21.3, 8.21.4, 8.21.5, 8.21.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007578IN-MAL-2026-007579IN-MAL-2026-009799GHSA-4mc4-4rf2-2cm6IN-MAL-2026-010408IN-MAL-2026-010413IN-MAL-2026-010473

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @dervix/ws-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@dervix/ws (npm) malicious package — MAL-2026-6496 | O3 Security