Which versions of @db-tools/main-app are malicious?

The following npm versions of @db-tools/main-app are flagged malicious: 2026.6.30. Treat any of these as compromised.

How do I remediate @db-tools/main-app if I installed it?

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.

I already installed @db-tools/main-app — how do I know if it already compromised me?

If @db-tools/main-app 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.

Is @db-tools/main-app part of a known attack campaign?

Yes — @db-tools/main-app is associated with the IN-MAL-2026-009800 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @db-tools/main-app across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @db-tools/main-app (version 2026.6.30). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @db-tools/main-app across your stack and pipelines.

Malicious package

@db-tools/main-appnpm

Malicious code in @db-tools/main-app (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @db-tools/main-app (version 2026.6.30). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @db-tools/main-app across your stack and pipelines.
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.
Did it already run?
If @db-tools/main-app 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 @db-tools/main-app 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

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

npmjs.com

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