Which versions of gym-reschdule-combination are malicious?

The following PyPI versions of gym-reschdule-combination are flagged malicious: 93.6. Treat any of these as compromised.

How do I remediate gym-reschdule-combination if I installed it?

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

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

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

Malicious package

gym-reschdule-combinationPyPI

Malicious code in gym-reschdule-combination (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10592

Immediate action

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

pip uninstall gym-reschdule-combination

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 'gym-reschdule-combination' @ 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)

28c5e3a715162d4730a613b21ab2d2b7533a9f5f0fdfdc33e41128190edbe7c3

eed05750b9a94656bad51411969ffa9b6ae30795da729e98fe748f191c7750b7

9d6896ff82aa630b84126788fe76a7c577e11e871c9307f5b56a43ea7166062d

5654be4bb5583f7c5143294f7ec6c3488311de746efcd2a862b2e303c9449647

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 gym-reschdule-combination (version 93.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gym-reschdule-combination across your stack and pipelines.
If you installed it — respond
gym-reschdule-combination 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 gym-reschdule-combination 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 gym-reschdule-combination 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. gym-reschdule-combination 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 gym-reschdule-combination-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