db-connector-lognpm
db-connector-log is a confirmed malicious npm package (MAL-2026-6142) that opens a backdoor for remote access (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in db-connector-log (npm)
What this malware does
[email protected] impersonates the legitimate dx-db-connector package (divbloxjs); package.json's repository/homepage point at the divbloxjs project and the library code is a near-verbatim copy with one added method. DivbloxDatabaseConnector.queryDBConnect contains a base64 literal HASH_KEY ("aHR0cHM6Ly9qc29ua2VlcGVyLmNvbS9iL1NINVpX") that decodes via atob() to a jsonkeeper.com paste URL, fetches the.session field from that URL with axios, then spawns a detached node child process with stdio piped/ignored and writes the fetched string to its stdin for execution. This is fetch-and-exec of attacker-controlled, mutable remote JavaScript from an anonymous paste host, with the endpoint deliberately obfuscated via base64 encoding and a misleading variable name. Any consumer that invokes queryDBConnect (or any future release that wires this method into install/import paths) executes arbitrary attacker-controlled code in the installer's Node process. The combination of name impersonation of an established publisher, copy-paste of the victim package's code, an added remote-code-execution method, anonymous mutable code source, and URL obfuscation is the canonical typosquat dropper shape.
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
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for db-connector-log (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging db-connector-log across your stack and pipelines.
If you installed it — respond
db-connector-log establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If db-connector-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-connector-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-connector-log-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.