Which versions of smart-scheduler are malicious?

The following PyPI versions of smart-scheduler are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate smart-scheduler if I installed it?

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

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

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

Malicious package

smart-schedulerPyPI

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

MAL-2025-191661

Immediate action

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

pip uninstall smart-scheduler

What this malware does

Package downloads and starts a malicious executable and hides its existence

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

Campaign: 2025-10-smart-scheduler

Reasons (based on the campaign):

Downloads and executes a remote executable.
exfiltration-generic
obfuscation
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

5 flagged

0.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

09cc75b4443a5a40b87fa27844d57cd60340812c0ea4142a4bcc92f8b4618b61

aed28b68f5984a2fc03169c226b2739054a38a101ad7a32d394d1279a4dd89f8

2792dcc5f5baaa05e1da756d9e57efedf800477f8b30e3c0b096d0baa17f59c9

59e4b5ea012f00415434e6d2234bc2b593a3720c4a3c16db4fec2f1dd5e8c241

9dd9772bb51ac4755fb914f02065f88ecdc0a9e5d5f2524abd7fbe6834f2478b

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

Campaign

RLMA-2025-056382025-10-smart-schedulerRLUA-2026-00763

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks smart-scheduler-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