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

insomnia-test-util-m4gesternpm

Malicious code in insomnia-test-util-m4gester (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6554
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall insomnia-test-util-m4gester

What this malware does

Package ships no functional code and exists solely to execute a shell command on npm install. The postinstall lifecycle hook runs echo PWNED_BY_DEEPLINK > /tmp/pwned.txt, dropping a marker file at /tmp/pwned.txt on the installer's machine. The self-identifying marker string (PWNED_BY_DEEPLINK) confirms the package's only purpose is to demonstrate arbitrary install-time code execution against installers. The package name mimics the Insomnia (Kong) HTTP-client ecosystem naming convention while the publishing handle is unrelated, consistent with a lure/PoC namespace-abuse shape. Although the present payload is a benign marker write, the install-time arbitrary-command-execution primitive is fully wired and would execute any command the maintainer publishes in a future version.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

3af3f61639cfac47d91b75ec177ce18a07c29535b0f39806a286093e739494c8
fda634406b6f4fd97c572c7d4a52d6e3201932fea144a157e955aa16fa394da4

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for insomnia-test-util-m4gester (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-test-util-m4gester across your stack and pipelines.

  2. If you installed it — respond

    insomnia-test-util-m4gester is a typosquat — you almost certainly intended a legitimately-named package. Remove insomnia-test-util-m4gester, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If insomnia-test-util-m4gester 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-test-util-m4gester 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-test-util-m4gester 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-007693IN-MAL-2026-007694

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks insomnia-test-util-m4gester-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-test-util-m4gester (npm) malicious package — MAL-2026-6554 | O3 Security