Which versions of mod-manager are malicious?

The following npm versions of mod-manager are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate mod-manager if I installed it?

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

If mod-manager 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.

How do I find mod-manager across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mod-manager (2 malicious versions).

Malicious package

mod-managernpm

Advisory published Oct 30, 2025Updated Oct 1, 2026

mod-manager is a confirmed malicious npm package (MAL-2025-49233) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mod-manager (npm)

MAL-2025-49233

Immediate action

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

npm uninstall mod-manager

What this malware does

The package mod-manager was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

8ec890b586ea0ff47a8ba914ff95c535bdeebbdfaf6788b6357a5afae32c9463

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mod-manager (2 malicious versions).
If you installed it — respond
Remove mod-manager 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 mod-manager 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. mod-manager on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mod-manager-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