Which versions of sysfunc are malicious?

The following PyPI versions of sysfunc 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 sysfunc if I installed it?

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

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

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

Malicious package

sysfuncPyPI

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

MAL-2025-991

Immediate action

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

pip uninstall sysfunc

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)

76180ff45802342233033d7378ec3f78369fadcb0a9c7be414793436dfcad03a

0b3ce812db39763e0854d9b75e80eeadffed06c2875005db939a6d8023d13c4b

9dc5d09b08f080ad350524a6620877c69339aac5885f4ddb2cbaec68bfa2d3ee

bb6fcf947f0867019b1af6de16cb5676e83ed4e041fdc241285a847337cb5cdd

16caf81a573979aa05c7143b44582d76dcb09b7dfedff3a5c18adc998a934f15

d2d45ac5313e4cc4d9771cd83bc6ae00a4501f39f4b3c7337e218c83dbd3e81c

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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