MAL-2026-20295: Malicious code in @guicai777/mcp-doctor (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (239993ae4c14c460d6ee1558bb2808072cf850d91c451fe950752387d4edb179) The package ships bridge.bin (~866KB) as base64-encoded, XOR-obfuscated bytes. On Windows, index.js reads bridge.bin, base64-decodes it, XOR-decrypts it with a one-byte key taken from the first byte of the blob, writes the resulting PE to %LOCALAPPDATA%\mcp-doctor\mcp-bridge.exe, and spawns it detached with windowsHide: true and stdio: 'ignore'. Before dropping, the CLI fetches https://fix-mcp-bridge.com/v.json and only skips execution when the remote JSON returns active:false, giving the operator a remote kill-switch to time and target payload activation. The README additionally instructs users to run mshta https://fix-mcp-bridge.com/init, a LOLBAS technique that downloads and executes remote HTML/JS/VBScript from the same author-controlled domain under the user's context. There is no legitimate build-time reason to base64+XOR a Windows binary the package itself owns; the encoding exists solely to conceal the payload's contents from scanners and reviewers, and the opaque PE is executed on the installer's host with no hash or signature verification. The combination of an obfuscated bundled executable, remote-gated drop-and-exec, and a documented out-of-band mshta remote-code-execution install path is a cover-story dropper masquerading as an MCP diagnostic utility.
Affected Software
Event History
Frequently Asked Questions
Which systems are exposed to the embedded executable payload?
The described executable-dropper behavior is specific to Windows. On Windows, the package decrypts a PE file, writes it to %LOCALAPPDATA%\mcp-doctor\mcp-bridge.exe, and starts it detached without visible console output.
What conditions control whether the payload runs?
Before dropping the executable, the CLI requests https://fix-mcp-bridge.com/v.json. Execution is skipped only if the returned JSON contains active:false, allowing the remote operator to control activation and timing.
What should be investigated on a Windows host that installed this package?
Check for %LOCALAPPDATA%\mcp-doctor\mcp-bridge.exe and determine whether it was executed. Also review requests to fix-mcp-bridge.com, including v.json and init, because the package and its README direct activity to that domain.
Is there an additional execution path beyond the packaged binary?
Yes. The README instructs users to run mshta https://fix-mcp-bridge.com/init, which downloads and executes remote HTML, JavaScript, or VBScript under the current user's context.