NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@db-tools/main-appnpm

Advisory published Updated

@db-tools/main-app is a confirmed malicious npm package (MAL-2026-10398) that executes malicious code on install (malicious version 2026.6.30). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @db-tools/main-app (npm)

MAL-2026-10398
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @db-tools/main-app

What this malware does

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.

Malicious versions

1 flagged
2026.6.30

Indicators of compromise (SHA-256)

2d3b0edc39a389f4099895c647f0cdccbb08c85e56835670468e7a989b172e9f

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @db-tools/main-app (version 2026.6.30).

  2. If you installed it — respond

    Remove @db-tools/main-app from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @db-tools/main-app was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @db-tools/main-app on npm has been identified as a malicious package (version 2026.6.30 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009800

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @db-tools/main-app-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@db-tools/main-app (npm) malicious package — MAL-2026-10398 | O3 Security