Which versions of pysbark are malicious?

The following PyPI versions of pysbark are flagged malicious: 0.21.0. Treat any of these as compromised.

How do I remediate pysbark if I installed it?

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

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

Yes — pysbark is associated with the RLMA-2024-11132, GENERIC-standard-pypi-install-pentest, RLUA-2026-00645 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 pysbark 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 pysbark (version 0.21.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pysbark across your stack and pipelines.

Malicious package

pysbarkPyPI

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

MAL-2024-11675

Immediate action

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

pip uninstall pysbark

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.21.0

Indicators of compromise (SHA-256)

46b109a80ac5a539aa33147c070f0b4aace716e3e88ecb294516e318b8c09ebd

e10e0dda82e93ace6a101381f9ef255a01ff0dd9a0a0d6c7f1d1c793e983e9ec

8eb82be602cc0d4c10e768559d90db6457348a41e6e789d8bd6f7c31387b099e

698a4d1095ac322ea753f36a7b56bdbb90ef9d17d144034064b58d12fd6f1ecc

4995d9ad89d57f95e434a672e9278e1528d22373492b8fa48ad0099fba58ecb2

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

Campaign

RLMA-2024-11132GENERIC-standard-pypi-install-pentestRLUA-2026-00645

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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