Supply Chain - Warden DB MCP Linux x64 Package Execution
This rule flags when a specific npm package, @rodrigodotdev/warden-db-mcp-linux-x64, gets pulled in and run on a system. It arrives automatically as a hidden dependency of the warden-db-mcp package rather than something a developer chooses to install directly, and its publisher and purpose have not been verified.
How the attack works
A developer or CI pipeline installs the warden-db-mcp package, which silently drags in @rodrigodotdev/warden-db-mcp-linux-x64 as a transitive dependency. Package managers like npm, npx, yarn, or pnpm then run an install or postinstall step that extracts and can execute the bundled Linux x64 binary. The rule watches for any process spawn whose command line references this package's path, whether that happens during install, through a postinstall hook, or by someone directly running the extracted binary. This gives an unreviewed, third-party binary a path onto the machine and into execution without the installer explicitly agreeing to run it.
Netzilo detection
Netzilo reports this behaviour when it is observed.
- Signature ID
- 7f3c9d2e-4b6a-4f18-9d3e-2a6b7c8e1f0a
- Severity
- High
Why it matters
An organization could end up running unvetted, unsigned code on build or developer machines without deliberately choosing to, giving an unverified third party a foothold for whatever the binary actually does — from data exfiltration to further supply-chain compromise.
What you can do
- →Audit package.json and lockfiles for warden-db-mcp and its transitive dependency @rodrigodotdev/warden-db-mcp-linux-x64 before allowing installs.
- →Pin dependencies and use lockfile integrity checks so transitive packages can't silently change or add binaries.
- →Disable or restrict postinstall/lifecycle scripts in CI and developer environments unless explicitly required.
- →If the package is found running, isolate the host, inspect the binary's behavior, and treat it as an unverified third-party artifact until proven benign.
Known benign look-alikes
- Running `npm view @rodrigodotdev/warden-db-mcp-linux-x64`, `npm info`, or similar registry metadata lookups during a manual dependency audit
- Security or SBOM tooling (`npm audit`, `grep`, `rg`, `find`, `jq`) scanning package.json / package-lock.json / node_modules for the package name as part of a supply-chain review
- Directory listing or inspection commands (`ls`, `tree`, `cat`, `file`, `du`) run against node_modules that happen to include the package path in their arguments without invoking the bundled binary