Which versions of ultra-ws are malicious?

The following npm versions of ultra-ws are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ultra-ws if I installed it?

Remove ultra-ws 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 ultra-ws — how do I know if it already compromised me?

If ultra-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.

Is ultra-ws part of a known attack campaign?

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

Malicious package

ultra-wsnpm

ultra-ws is a confirmed malicious npm package (MAL-2026-16155) 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 ultra-ws (npm)

MAL-2026-16155

Immediate action

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

npm uninstall ultra-ws

What this malware does

package.json declares a dependency node-net-pool whose source is a tarball URL on the main branch of a random third-party GitHub account (https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz) rather than a registry version range. On npm install, npm fetches whatever bytes that URL currently returns, unpinned and integrity-unchecked, and executes any lifecycle scripts contained in the fetched package. The postinstall script additionally invokes node -e "... require('node-net-pool')...", so the fetched module's top-level code runs in the installer's Node process at install time. The owner account name is a random throwaway-shaped identifier unrelated to any declared publisher, and the branch is mutable so the delivered code can change at any moment without a version bump.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a3cd852fb9e34a4705cad99a8022db52461e1325daddfa1425df17bbc3b7ac08

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ultra-ws (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ultra-ws across your stack and pipelines.
If you installed it — respond
Remove ultra-ws 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 ultra-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.
How O3 protects you
O3 blocks ultra-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. ultra-ws 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-020042

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ultra-ws-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