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

mad-10.1.1.2.2.8npm

mad-10.1.1.2.2.8 is a confirmed malicious npm package (MAL-2025-48250) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mad-10.1.1.2.2.8 (npm)

MAL-2025-48250
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mad-10.1.1.2.2.8

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

43b7ae35d8522c82d7af230bc72f76eafab00194667d0a543b69f62c609e769b
ad47a071994b9bd2285f5e925e2463f0ed0efee3253a235b7544e647c6d129af
a7aba7a529ecddf77785dedad0b6340a038903e612917615b9c1d6a8a76cd03a

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 mad-10.1.1.2.2.8 (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 mad-10.1.1.2.2.8 across your stack and pipelines.

  2. If you installed it — respond

    Remove mad-10.1.1.2.2.8 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 mad-10.1.1.2.2.8 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 mad-10.1.1.2.2.8 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. mad-10.1.1.2.2.8 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

GHSA-q7pc-p72v-pxgpRLMA-2025-05412RLUA-2025-05872

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks mad-10.1.1.2.2.8-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

mad-10.1.1.2.2.8 (npm) malicious package — MAL-2025-48250 | O3 Security