MAL-2026-10398 Malicious code in @db-tools/main-app (npm)
Malicious package
Published
MAL-2026-10398 is a malicious package: @db-tools/main-app (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-10398/ (Markdown: https://insights.sbomify.com/MAL-2026-10398/index.md)
- Package
- @db-tools/main-app
- Registry
- npm
What is MAL-2026-10398?
MAL-2026-10398 is a malicious package in @db-tools/main-app, published on 13 Jul 2026.
Official description
package.json declares a preinstall hook
npm install @sentry/node && node examples/verify.js that fires on every npm install. examples/verify.js calls the library's init() with no DSN, which falls back to a hardcoded DEFAULT_DSN in src/index.js (https://[email protected]/4511652667785296). verify.js then invokes setUserFromPublicIp() which fetches the installer's public egress IP from https://www.cloudflare.com/cdn-cgi/trace, attaches it as Sentry user context, throws a synthetic exception, and flushes it to the author-controlled Sentry project. The installer has no opportunity to configure or opt out — the data flow is unconditional and non-consensual on npm install. Separately, the exported init() API uses the same hardcoded DEFAULT_DSN as its final fallback (after options.dsn and process.env.SENTRY_DSN) and sets sendDefaultPii: true, so any consumer that uses the library without explicitly supplying a DSN silently routes their application's exceptions and PII to the same author-owned Sentry project, with no disclosure in the README.What should I do about MAL-2026-10398?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.