Which versions of db-convertor are malicious?

The following npm versions of db-convertor are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate db-convertor if I installed it?

db-convertor 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.

I already installed db-convertor — how do I know if it already compromised me?

If db-convertor 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.

Is db-convertor part of a known attack campaign?

Yes — db-convertor is associated with the GHSA-p467-3jcx-48q5, IN-MAL-2026-009336 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find db-convertor across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for db-convertor (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging db-convertor across your stack and pipelines.

Malicious package

db-convertornpm

db-convertor is a confirmed malicious npm package (MAL-2026-6726) that opens a backdoor for remote access (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in db-convertor (npm)

MAL-2026-6726

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall db-convertor

What this malware does

index.js defines a method queryDBConnect on the exported DivbloxDatabaseConnector class that base64-decodes a hardcoded constant HASH_KEY to the URL https://jsonkeeper.com/b/SH5ZW, fetches the session field from that JSON paste via axios, and pipes the returned content as stdin into a detached node child process. The fetched bytes are executed without inspection, hashing, signing, or origin checks. jsonkeeper.com is an anonymous mutable paste host — the operator can swap the payload at any time, so any caller who reaches this method runs arbitrary attacker-controlled code in the installer's Node process. The endpoint is obscured behind a base64 literal and atob() to evade casual review and string scanners, and the method is undocumented in the README and unrelated to the package's stated database-connection purpose. The package name (db-convertor) and keywords (divblox, dx-db-connector) impersonate the legitimate Divblox dx-db-connector package, increasing the likelihood that an installer who mistypes the dependency ends up with this backdoored class.

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

1 flagged

1.0.5

Indicators of compromise (SHA-256)

325a83367699f226bf706d6847891a07256202cb73998bc9866eb485132d2a2a

7480b95a12688a84f3efd3d4c5c8a82c5c761f1f462eb22201f4385fb9bf691c

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for db-convertor (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging db-convertor across your stack and pipelines.
If you installed it — respond
db-convertor 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-convertor 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-convertor 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

No. db-convertor on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p467-3jcx-48q5IN-MAL-2026-009336

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks db-convertor-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database