MAL-2026-5403 Malicious code in t-invest-mcp-server (npm)
Malicious package
Published
MAL-2026-5403 is a malicious package: t-invest-mcp-server (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-5403/ (Markdown: https://insights.sbomify.com/MAL-2026-5403/index.md)
- Package
- t-invest-mcp-server
- Registry
- npm
What is MAL-2026-5403?
MAL-2026-5403 is a malicious package in t-invest-mcp-server, published on 9 Jun 2026.
Official description
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.What should I do about MAL-2026-5403?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.