Which versions of mcp-audit-sync-internal are malicious?

The following npm versions of mcp-audit-sync-internal are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate mcp-audit-sync-internal if I installed it?

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

If mcp-audit-sync-internal 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 mcp-audit-sync-internal part of a known attack campaign?

Yes — mcp-audit-sync-internal is associated with the IN-MAL-2026-014705 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 mcp-audit-sync-internal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mcp-audit-sync-internal (version 99.9.9).

Malicious package

mcp-audit-sync-internalnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

mcp-audit-sync-internal is a confirmed malicious npm package (MAL-2026-12401) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mcp-audit-sync-internal (npm)

MAL-2026-12401

Immediate action

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

npm uninstall mcp-audit-sync-internal

What this malware does

[email protected] declares scripts.preinstall = 'node index.js'. On Windows, index.js spawns a hidden PowerShell process that fetches a ZIP from https://files.catbox.moe/5khq55.zip, expands it into %TEMP%, and then Start-Process's the extracted Verification_Tool.exe. The remote artifact is unpinned, unverified (no hash or signature check), delivered from an anonymous throwaway file host unrelated to the package publisher, and the fetch/execute is hidden from the user via -WindowStyle Hidden. This fires automatically on npm install, yielding arbitrary code execution on any Windows installer's host. Package metadata ('Administrative sync tool for corporate environments', author 'IT Compliance') and the 'Verification_Tool.exe' filename are cover-story framing that mismatches the actual behavior; the 99.9.9 version is a placeholder-sentinel shape.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

897822fdfb08c83d7d949c16e497d6897b9b679cc2f05a0409b1ec369a1f10fc

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-014705

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mcp-audit-sync-internal-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