Which versions of http-ws-listener are malicious?

The following npm versions of http-ws-listener are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate http-ws-listener if I installed it?

http-ws-listener establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed http-ws-listener — how do I know if it already compromised me?

If http-ws-listener 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 http-ws-listener part of a known attack campaign?

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

Malicious package

http-ws-listenernpm

http-ws-listener is a confirmed malicious npm package (MAL-2026-10623) that opens a backdoor for remote access (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in http-ws-listener (npm)

MAL-2026-10623

Immediate action

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

npm uninstall http-ws-listener

What this malware does

[email protected] ships misc/configFetcher.js, which reconstructs a hidden Pastebin URL and the module names 'net' and 'child_process' by triple-base64-decoding a Lorem-ipsum string literal and indexing characters through a numeric array. When the package's advertised entrypoint startWebSocketServer() is called, fetchConfig() retrieves colon-separated handles from the paste, dynamically imports the built-in net and child_process modules, invokes child_process.exec on a second remote-fetched string, opens a TCP socket to a host:port also carried in the paste, and pipes that socket into the child process's stdin, stdout, and stderr. The result is an interactive reverse shell on the machine running the package, driven by content that the paste author can mutate at any time. The obfuscation (triple base64 plus character-index reconstruction) exists to hide the C2 URL and the built-in module names from static inspection.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

2b70acc8a626218c5855ef656a6945f1f2018c0ff62c112d9b31bae5016fae49

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for http-ws-listener (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging http-ws-listener across your stack and pipelines.
If you installed it — respond
http-ws-listener establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If http-ws-listener 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 http-ws-listener 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. http-ws-listener on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010564

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks http-ws-listener-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database