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

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?

Search your lockfiles and build artifacts for module-listener (all published versions).

Malicious package

module-listenernpm

Advisory published Dec 5, 2025Updated Dec 5, 2025

module-listener is a confirmed malicious npm package (MAL-2025-192308) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in module-listener (npm)

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
Search your lockfiles and build artifacts for module-listener (all published versions).
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 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. 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

Explore

All malware advisories How O3 detects malware Vulnerability database