Which versions of module-listener are malicious?

Every published version of module-listener on npm is considered malicious. Remove the package entirely.

How do I remediate module-listener if I installed it?

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

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

Yes — module-listener is associated with the GHSA-8r5p-ph77-4q47 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 module-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 module-listener (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging module-listener across your stack and pipelines.

Malicious package

module-listenernpm

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

MAL-2025-192308

Immediate action

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

npm uninstall module-listener

What this malware does

The package module-listener was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c922f84811ce200feff2b048957a9b81b6e78d33db6abc439c1ce9ef7a0950a4

d17f403951ae366e78ffa76ef093fdbeb3bd4fa3de3b9753c8d7b56fea6bede2

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

Campaign

GHSA-8r5p-ph77-4q47

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks module-listener-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