Which versions of opshub are malicious?

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

How do I remediate opshub if I installed it?

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

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

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

Malicious package

opshubPyPI

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

MAL-2025-948

Immediate action

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

pip uninstall opshub

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

1 flagged

0.1

Indicators of compromise (SHA-256)

9446bc1312484ae2f46670c02b14f188213b37a968baa383eb2b9cc7f039119f

f6404ffc1493d86c2d4fa409e39b694070f54a086ecc4b9a41277755c4e6f6d1

b758593c8b18a483c8bb0309dd1e2bf37c40853f5c0a203327508c54de12bb56

965e1b24b0012971eb17d686b45c0c440ba928247401f187367eb048b9586039

977d4a816c60016146512fc73cf37c8287b6811b439d46b767ab5407a899114e

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 opshub (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging opshub across your stack and pipelines.
If you installed it — respond
opshub 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 opshub 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 opshub 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. opshub 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-2025-004892024-12-syscontrolRLUA-2026-00569

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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