db-query-lognpm
Malicious code in db-query-log (npm) Remove it immediately and rotate any exposed credentials.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for db-query-log (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-query-log across your stack and pipelines.
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 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-query-log 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
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.