db-query-lognpm
Advisory published Updated
db-query-log is a confirmed malicious npm package (MAL-2026-6539) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in db-query-log (npm)
What this malware does
The package presents itself as a database query helper but index.js defines a method queryDBConnect() that base64-decodes a hardcoded URL pointing to https://www.jsonkeeper.com/b/ZIAIK (an anonymous, attacker-mutable JSON paste host), fetches the.data.content field via axios, and compiles and executes the response as a Node module via new Module()._compile(...). The destination URL is stored as a base64 literal named HASH_KEY and decoded with atob() at runtime, hiding it from static inspection, and errors in the fetch-and-execute path are silently swallowed. Package metadata further misrepresents the project: package.json declares the name 'db-query-log' while repository/homepage/bugs all point to github.com/divbloxjs/dx-db-connector and the exported class is DivbloxDatabaseConnector, with the remote-exec method absent from that upstream's API. Any consumer that calls into the package's connector and reaches this code path will execute arbitrary attacker-controlled JavaScript inside the Node.js process with the installer's privileges.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for db-query-log (2 malicious versions).
If you installed it — respond
Remove db-query-log 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-query-log 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks db-query-log-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.