Which versions of pycblines are malicious?

The following PyPI versions of pycblines are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pycblines if I installed it?

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

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

Yes — pycblines is associated with the RLMA-2024-11126, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00623 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 pycblines 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 pycblines (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pycblines across your stack and pipelines.

Malicious package

pycblinesPyPI

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

MAL-2024-11669

Immediate action

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

pip uninstall pycblines

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1be6fdb3df3d77c79b16028da8ef6a0153e3d199b8cfdfcef52406a248efbe47

19442f090f7b47c44b9995a5434b117f965b6b9627712dc20eda52eed982b732

003ff4ad180c7d33db185b8c29ceca2689909864b5e36c450eb8125290365f99

8c55e5679fb06d6313c63b7c8ed1b5e9cd8903e2f0e306945f43e9f340a63534

7bce62bf17a19ab44f8315a15effce85f4c28a018961e20c381e0b6c0270b594

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

Campaign

RLMA-2024-111262024-08-embeds-RealtekHDAudioManagerRLUA-2026-00623

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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