Which versions of service-affinity-scheduling are malicious?

The following PyPI versions of service-affinity-scheduling are flagged malicious: 99.6. Treat any of these as compromised.

How do I remediate service-affinity-scheduling if I installed it?

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

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

Yes — service-affinity-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 service-affinity-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 service-affinity-scheduling (version 99.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging service-affinity-scheduling across your stack and pipelines.

Malicious package

service-affinity-schedulingPyPI

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

MAL-2024-10838

Immediate action

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

pip uninstall service-affinity-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 'service-affinity-scheduling' @ 99.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.6

Indicators of compromise (SHA-256)

1450f3c4b76e04809a27533c2613ac0ff962d0bfeb4d69c364fdd35ccd8f9815

357bc353b39a461243d903395448d4e580c6936303d6a68acd123b13b518ed82

68be996c62ae54a32b5613110a7d66dcd40d443ca8fc6e8e869731be7ff40833

7de4d49277eb2a476d234e994072c88a8d17f8693b960a673fcfbf02605df391

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 service-affinity-scheduling (version 99.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging service-affinity-scheduling across your stack and pipelines.
If you installed it — respond
service-affinity-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 service-affinity-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 service-affinity-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. service-affinity-scheduling on PyPI has been identified as a malicious package (version 99.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 service-affinity-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