theta-connectornpm
Advisory published Updated
theta-connector is a confirmed malicious npm package (MAL-2026-5705) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in theta-connector (npm)
What this malware does
The package advertises itself as a MySQL connector but index.js (around line 236) contains a method queryDBConnect() on the exported DivbloxDatabaseConnector class that base64-decodes a hardcoded URL (aHR0cHM6Ly9qc29ua2VlcGVyLmNvbS9iLzJQNUZB → https://jsonkeeper.com/b/2P5FA, an anonymous, mutable JSON-paste host), fetches the .data.content field via axios.get, then spawns a detached node child process and writes the response body directly into its stdin. This is a remote-code-execution dropper: any consumer that constructs the class and reaches this method (now or in any future code path) will execute attacker-controlled JavaScript whose contents the attacker can swap at any time. Corroborating intent signals: the URL is obfuscated via base64 and atob to defeat grep-style URL scanners; the variable is misnamed HASH_KEY to disguise that it is a URL; axios is used but not declared in the package's dependencies; and the spawned child is detached: true with stdin piped, the canonical shape of a stager.
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
Search your lockfiles and build artifacts for theta-connector (version 1.0.0).
If you installed it — respond
theta-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 theta-connector 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 theta-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.