Which versions of syschecker are malicious?

The following PyPI versions of syschecker are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate syschecker if I installed it?

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

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

Yes — syschecker is associated with the RLMA-2025-05641, 2025-10-windowsrequir, RLUA-2026-00794 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 syschecker 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 syschecker (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging syschecker across your stack and pipelines.

Malicious package

syscheckerPyPI

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

MAL-2025-191663

Immediate action

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

pip uninstall syschecker

What this malware does

Package downloads and runs an obfuscated bat file, which executes malicious activity according to VirusTotal results.

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

Campaign: 2025-10-windowsrequir

Reasons (based on the campaign):

impersonation
Downloads and executes a remote malicious script.
malware

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d0e2650f83ac021e35ac310d0c8c619f764d830aa00946ad88216d551896d019

9a4acaadc3325f04ceaef679cde8994c5c045700d666cf5c25f9a5448b0f0bea

81ab746bf511a8c6c41c5776e5688c310a5255c65fda0fad65e31b1ed534dc91

f77109832365fbab9dbaad573144434177c5aee8f4913471d83de2728c1353fe

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

Campaign

RLMA-2025-056412025-10-windowsrequirRLUA-2026-00794

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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