Which versions of hello-bozzo2 are malicious?

The following PyPI versions of hello-bozzo2 are flagged malicious: 1.2.3. Treat any of these as compromised.

How do I remediate hello-bozzo2 if I installed it?

Remove hello-bozzo2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hello-bozzo2 — how do I know if it already compromised me?

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

Yes — hello-bozzo2 is associated with the GENERIC-simple-tests 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 hello-bozzo2 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 hello-bozzo2 (version 1.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hello-bozzo2 across your stack and pipelines.

Malicious package

hello-bozzo2PyPI

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

MAL-2024-12283

Immediate action

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

pip uninstall hello-bozzo2

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.2.3

Indicators of compromise (SHA-256)

709073a1b8981b5a55e03d50a8a719f4d724c912346b655df13bb00cc4f90ba4

96e02710356e7f0a4dee853d165a2d18a0a4addad3a07c397e495f61f6bc92fa

130fd6e9fa0d6e562becaebc0fd1b3a37765ffa00b842bafee60ffbe503066fc

66062873aaad48ddad163373f6dd3a8a5a5a750ca3fc13c905dc0ca76db09fa2

552975114062da9797ca0ff5a575e3c948832f4b1c7c385fa7b6a8998d7c23a7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hello-bozzo2 (version 1.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hello-bozzo2 across your stack and pipelines.
If you installed it — respond
Remove hello-bozzo2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hello-bozzo2 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 hello-bozzo2 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. hello-bozzo2 on PyPI has been identified as a malicious package (version 1.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks hello-bozzo2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring