What does the dbsxrchpro malware do?

Installing the package starts downloading and installing an Infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2024-12-graphicsx Reasons (based on the campaign): - The package overrides the install command in setup.py to execute malicious code during installation. - obfuscation - Downloads and executes a remote executable. - infostealer - exfiltration-browser-data

Which versions of dbsxrchpro are malicious?

The following PyPI versions of dbsxrchpro are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate dbsxrchpro if I installed it?

dbsxrchpro is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed dbsxrchpro — how do I know if it already compromised me?

If dbsxrchpro 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 dbsxrchpro part of a known attack campaign?

Yes — dbsxrchpro is associated with the RLMA-2025-01953, 2024-12-graphicsx, RLUA-2026-00252 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 dbsxrchpro 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 dbsxrchpro (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbsxrchpro across your stack and pipelines.

Malicious package

dbsxrchproPyPI

Malicious code in dbsxrchpro (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2955

Immediate action

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

pip uninstall dbsxrchpro

What this malware does

Installing the package starts downloading and installing an Infostealer

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-12-graphicsx

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
Downloads and executes a remote executable.
infostealer
exfiltration-browser-data

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

f24cf88528ac0b972f5950c252ecdd65e5cf3c464f3ffcb37736ccef8d30f3cf

cff61bb284a330df556b40eed4f40e4704ffba2c51bd1d59c494204ae5426d55

f7e904380115b3ea3cfb5766a5e527bb71775c65af3706c2d5392ef3e60d17c5

0648eb9045a250821c283a3a92452fcdb0588d8aab60edb5fa8cda68b9102940

43dd5da51a3b09b7d25d944ff9b1575cda8ff249fa626f6738f3a8b1597bdbeb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dbsxrchpro (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbsxrchpro across your stack and pipelines.
If you installed it — respond
dbsxrchpro is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dbsxrchpro 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 dbsxrchpro 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. dbsxrchpro on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-019532024-12-graphicsxRLUA-2026-00252

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks dbsxrchpro-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring