Which versions of example-pypi-package-loler1 are malicious?

The following PyPI versions of example-pypi-package-loler1 are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate example-pypi-package-loler1 if I installed it?

Remove example-pypi-package-loler1 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 example-pypi-package-loler1 — how do I know if it already compromised me?

If example-pypi-package-loler1 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 example-pypi-package-loler1 part of a known attack campaign?

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

Malicious package

example-pypi-package-loler1PyPI

example-pypi-package-loler1 is a confirmed malicious PyPI package (MAL-2024-12267) that executes malicious code on install (malicious version 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in example-pypi-package-loler1 (PyPI)

MAL-2024-12267

Immediate action

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

pip uninstall example-pypi-package-loler1

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

0.2.0

Indicators of compromise (SHA-256)

bb9d0ffae446884323ea67cfef5b0e47042d1c01c0a87d9fae2a14a1967aa94c

bb19218b6d780973bde55d613a16a9a637728a4d01e79d570bb3406633f0f639

4baf963b14275ac94f0403aff37d1776d40fa2666b5a93b09554f99294aeae7d

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

Explore

All malware advisories How O3 detects malware Vulnerability database