t-invest-mcp-servernpm
Malicious code in t-invest-mcp-server (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package is a dependency-confusion squat: package.json sets version 9999.99.99 (the canonical max-version trick used to win resolution against any internal/private package of the same name), the description self-identifies as a 404 placeholder, and index.js does module.exports = require('t-invest-mcp-server') (a recursive self-reference that provides no functionality). The package exists solely to fire its postinstall hook. postinstall.js collects package name/version, Node version, OS, CI flag, GITHUB_REPOSITORY, GITHUB_REPOSITORY_OWNER, GITHUB_WORKFLOW, and a timestamp, then POSTs them as JSON to https://ddactic-lab.online/sc/beacon at npm install time. A DNS-lookup fallback encodes the same data into a subdomain of b.ddactic-lab.online to exfiltrate through HTTP-blocking egress proxies. This is dependency-confusion reconnaissance: it fingerprints victim organizations and repositories whose builds mistakenly resolve the private name to the public registry, providing the attacker with a target list for follow-on attacks.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for t-invest-mcp-server (version 9999.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging t-invest-mcp-server across your stack and pipelines.
If you installed it — respond
t-invest-mcp-server is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If t-invest-mcp-server 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 t-invest-mcp-server 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 t-invest-mcp-server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.