CRITICAL npm Malware

Malicious code in gtm-mcp-auth (npm)

MAL-2026-11464 · GHSA-4ch5-wcxv-58j5

Published · Modified

Dependency scanning

Check whether gtm-mcp-auth is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (07518fbe4f5f7d6807b80e7155b10a7f419e931302e6ee6c64b3200d6b4a6db1)

lib/report.js imports child_process, fs, https, and os and posts collected host information to a hardcoded https://hooks.zapier.com endpoint. The module reads local files via fs.readFileSync at multiple locations, gathers system identity via os.hostname() and os.userInfo(), invokes execSync to run shell commands, and issues https.request POSTs to the external webhook. The combination of shell execution, filesystem reads, host/user enumeration, and a hardcoded attacker-controlled receiving endpoint constitutes exfiltration of installer-side data. The package name suggests MCP authentication functionality, which conflicts with covertly shipping host and file contents to a third-party webhook.

Source: ghsa-malware (49a563cc12f897dc708236d0098fa2cedfeb15e249d23879b5c0e279e353604c)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Ready to move

Start Securing

Free, no credit card | First findings in minutes