Which versions of rl-vm-scheduling are malicious?

The following PyPI versions of rl-vm-scheduling are flagged malicious: 93.6. Treat any of these as compromised.

How do I remediate rl-vm-scheduling if I installed it?

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

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

Yes — rl-vm-scheduling is associated with the 2024-11-byted-dast 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 rl-vm-scheduling 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 rl-vm-scheduling (version 93.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rl-vm-scheduling across your stack and pipelines.

Malicious package

rl-vm-schedulingPyPI

Malicious code in rl-vm-scheduling (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10598

Immediate action

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

pip uninstall rl-vm-scheduling

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'rl-vm-scheduling' @ 93.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

93.6

Indicators of compromise (SHA-256)

c9d46b8a974a83d81c3c1614fbab1c89c75ebc4db451e01778f66a1248e0cfde

f61c6d398c9cde16d678688fe21691aaa29a101a1f1ebdf49b78eaa4a037c1f1

8870fa73789eeccaedbe34d9bcf74ee3b438699c49a0e5b984055bcb5c86542f

48ab23abbb0843bb0b022101dadbf6737a29a1393bf25251dcaf6205cee62a44

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks rl-vm-scheduling-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