Which versions of oscontrol are malicious?

The following PyPI versions of oscontrol are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8. Treat any of these as compromised.

How do I remediate oscontrol if I installed it?

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

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

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

Malicious package

oscontrolPyPI

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

MAL-2025-949

Immediate action

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

pip uninstall oscontrol

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

8 flagged

0.10.20.30.40.50.60.70.8

Indicators of compromise (SHA-256)

2af57448e811c5d697d40bbaae005efb747f93d0609907026903a1b9fd879a37

0ddb4610616f7065ab6a96173bb37e346a73cb61907dbc53ebb9e30890b558eb

3ca9bc9d7a487115828ca20244ab570d82b479055acf3bc67da2387db377cc09

aba8f5b3f8384ac06569762cbf11e06c5c4266ced7de351cfba8ba5a9c400101

89cb7a89614a511c0e3e01fabe14382fd6833f55794a63a40f97376934d6d3bd

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

Campaign

RLMA-2025-004902024-12-syscontrolRLUA-2026-00575

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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