db-dx-connectornpm
Malicious code in db-dx-connector (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The package name db-dx-connector inverts the word order of the legitimate dx-db-connector package (whose own GitHub URL github.com/divbloxjs/dx-db-connector is referenced in this package's metadata). It replicates the legitimate package's MySQL-connector API surface and adds an undocumented method queryDBConnect in index.js (lines 226-238) that constitutes a backdoor: a base64-encoded URL stored in a misleadingly named HASH_KEY constant decodes to https://www.jsonkeeper.com/b/ZIAIK (an anonymous, mutable paste-hosting service), the method fetches .data.content from that URL via axios, constructs a synthetic Node module, and calls m._compile(s1, 'error.js') to execute the fetched JavaScript inside the consumer's Node process. Errors are silently swallowed in a try/catch. Whoever controls the paste can ship arbitrary code into any process that calls queryDBConnect(). The combination of name inversion against a real package, base64 URL obfuscation, anonymous attacker-controlled host, runtime fetch+compile of remote JavaScript, and silent error suppression is an unambiguous remote-code-execution backdoor.
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-dx-connector (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging db-dx-connector across your stack and pipelines.
If you installed it — respond
db-dx-connector 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-dx-connector 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-dx-connector 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-dx-connector-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.