Which versions of confighum are malicious?

The following PyPI versions of confighum are flagged malicious: 0.3.5. Treat any of these as compromised.

How do I remediate confighum if I installed it?

confighum 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 confighum — how do I know if it already compromised me?

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

Yes — confighum is associated with the RLMA-2025-03573, RLUA-2025-04132, 2025-07-0x9xnx, RLUA-2026-00220 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 confighum 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 confighum (version 0.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging confighum across your stack and pipelines.

Malicious package

confighumPyPI

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

MAL-2025-6482

Immediate action

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

pip uninstall confighum

What this malware does

Series of packages mostly with an obfuscated infostealer attempting to collect Chrome data. While discord webhook is usually set to an example, there are other, correct uploading URLs

Some of related packages only test partial malicious code, like webhooks from overwritten setup.py

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

Campaign: 2025-07-0x9xnx

Reasons (based on the campaign):

infostealer
obfuscation
exfiltration-browser-data
exfiltration-crypto
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.3.5

Indicators of compromise (SHA-256)

ca727db60ee7e06d2585cfa6fa45d79769dc0088f159e72182d9034dd9247c78

fea5a4ad0eedbf123c02f1c5e46a5bdf8ed6ce2ec8b5b002aa1043bd2263f81e

511ffd6fba9383efcec010bdbd12b19e237a79e473dff14a511a8fc9f2e368ba

48541202bca35853be1841a589b97e639fd36966f0d88900d11ff28be1b85b61

2195a301afe9c87930da8d0b5cc6bbb3c19a5096b68fabcdbef65da1d5769640

47b7e6787caa223fbc2581af974d868ffe96c545f273484cc341b81552b89b29

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 confighum (version 0.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging confighum across your stack and pipelines.
If you installed it — respond
confighum 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 confighum 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 confighum 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. confighum on PyPI has been identified as a malicious package (version 0.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03573RLUA-2025-041322025-07-0x9xnxRLUA-2026-00220

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks confighum-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