Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

mmppnpm

mmpp is a confirmed malicious npm package (MAL-2024-9283) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mmpp (npm)

MAL-2024-9283
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mmpp

What this malware does

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.

The OpenSSF Package Analysis project identified 'mmpp' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged
1.0.11.0.2

Indicators of compromise (SHA-256)

106eb5e2153c2a959cd0fc386d86d2ee43dfa8059e1092e33eb27f68d6623fdb
0e1f09e47e4834a51fb8c29b95da28cfefb88513869e96211a1ed18346be7cbb
19e1d61143b91e405fc0bf1401f3def53b01efefc28bfed53a58995d4dd41153

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mmpp (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mmpp across your stack and pipelines.

  2. If you installed it — respond

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

  3. Did it already run?

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

  4. How O3 protects you

    O3 blocks mmpp 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. mmpp on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qhpm-c6pv-4cxc

References

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks mmpp-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.

Explore

mmpp (npm) malicious package — MAL-2024-9283 | O3 Security