mcp-audit-sync-internalnpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-audit-sync-internal (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-audit-sync-internal across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks mcp-audit-sync-internal before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
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.