Which versions of package-lib8127 are malicious?

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

How do I remediate package-lib8127 if I installed it?

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

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

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

Malicious package

package-lib8127PyPI

Malicious code in package-lib8127 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11653

Immediate action

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

pip uninstall package-lib8127

What this malware does

Package contains CStealer, a known infostealer, starting on importing the module.

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

Campaign: 2024-09-cstealer

Reasons (based on the campaign):

infostealer
infostealer:cstealer

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

405c3386e34c4a6fca3f897cdbe4e9586c5cb5c6d279aee9aa2f156aabffabc7

d9d7feadd0badfdc1588fa10de040419c37b7a760ee8174c819c2b78b1b05749

2e0e446a5a40a8c6a1ea1041fa0fc875ef0dab2a8ad10cc74e459221906e6851

3cf0541bba671db30b333009f5916f72ed6f47323e49d2b7675bc508a7cc2606

f1058a08ee1c03de71c882d875c6652cddcd05f527c6d0f3f0dedade29730332

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 package-lib8127 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging package-lib8127 across your stack and pipelines.
If you installed it — respond
package-lib8127 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 package-lib8127 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 package-lib8127 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. package-lib8127 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-2024-111092024-09-cstealerRLUA-2026-00580

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks package-lib8127-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