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

insomnia-plugin-poc-m4gester2npm

Malicious code in insomnia-plugin-poc-m4gester2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6553
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall insomnia-plugin-poc-m4gester2

What this malware does

Package ships only a package.json with no plugin code, declaring a postinstall lifecycle script that runs echo PWNED_BY_DEEPLINK > /tmp/pwned.txt on every npm install. This writes a marker file to the installer's filesystem and demonstrates arbitrary command execution at install time. The package name self-identifies as a proof-of-concept (poc-m4gester) and adopts the insomnia-plugin-* namespace despite shipping no Insomnia plugin functionality. While the current payload is a benign marker write, the postinstall is an arbitrary-shell-on-install primitive with no legitimate purpose, in a namespace-squat shell of a package.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

1b2b63f22e7d0d8f23c608a3c109163e06e2bd6a1dd716305e0d8adaf6be6b86
a07696df593b382127f1eedea455af911e9e94591c0526d0b191576b411decf9

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 insomnia-plugin-poc-m4gester2 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging insomnia-plugin-poc-m4gester2 across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-007695IN-MAL-2026-007691

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks insomnia-plugin-poc-m4gester2-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.

insomnia-plugin-poc-m4gester2 (npm) malicious package — MAL-2026-6553 | O3 Security