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

ultimate-websocketnpm

Advisory published Updated

ultimate-websocket is a confirmed malicious npm package (MAL-2026-17529) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ultimate-websocket (npm)

MAL-2026-17529
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ultimate-websocket

What this malware does

package.json declares its only dependency node-net-pool as a bare tarball URL pointing at the mutable main branch of an unrelated GitHub user (https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz), bypassing the npm registry entirely. There is no version pin, no commit SHA, and no integrity hash, so npm install fetches whatever bytes that URL currently returns and runs any lifecycle scripts contained in them. The package's own scripts.postinstall additionally executes node -e "...require('node-net-pool')...", loading the fetched module at install time so its top-level code also runs on the installer's host. The GitHub account is a throwaway-shaped handle unrelated to the publishing identity, and the shipped tarball contains no real functionality — its only install-time effect is to pull and execute attacker-controlled code from an endpoint whose contents the author can change at any time.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

7574e423b830695141ee6e089006e0c355109e240c69881512806869cfee8114

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for ultimate-websocket (version 1.0.0).

  2. If you installed it — respond

    Remove ultimate-websocket 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.

  3. Did it already run?

    If ultimate-websocket 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. ultimate-websocket 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-020949

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ultimate-websocket-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.

Explore

ultimate-websocket (npm) malicious package — MAL-2026-17529 | O3 Security