Which versions of subsys-client are malicious?

The following PyPI versions of subsys-client are flagged malicious: 0.1, 0.2. Treat any of these as compromised.

How do I remediate subsys-client if I installed it?

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

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

Yes — subsys-client is associated with the RLMA-2025-00529, 2024-12-syscontrol, RLUA-2026-00784 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 subsys-client 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 subsys-client (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging subsys-client across your stack and pipelines.

Malicious package

subsys-clientPyPI

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

MAL-2025-988

Immediate action

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

pip uninstall subsys-client

What this malware does

Importing the module starts downloading and executing an Infostealer targeting browsers' and Discord data

In first packages, there was a hidden line triggering downloading and running an infostealer

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

Campaign: 2024-12-syscontrol

Reasons (based on the campaign):

infostealer
obfuscation
action-hidden-in-lib-usage
infostealer:kiwi
exfiltration-browser-data
exfiltration-crypto

Malicious versions

2 flagged

0.10.2

Indicators of compromise (SHA-256)

caa68805559269bccd60d7056f310073ad7977cb3ba96c05f7dccfd812238abf

a4c9023286b95175e83bff61b4a895f2fcbd0e48b6e66cc9f6daa62ef62e59bc

cd448fe7b92604e9718438328baa70266ded0a4e0c105f7663c9256b6eeea18b

9f489a70860edf070aad7df8d9fbc44635c03d2cd51fbb1e4c0edaa9f882ce51

52a97a2d7cb19c5be050fb3cd226ad5456a9186b47d2c433134deb4a3d1f466a

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

Campaign

RLMA-2025-005292024-12-syscontrolRLUA-2026-00784

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks subsys-client-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