Which versions of lobomarinopython are malicious?

The following PyPI versions of lobomarinopython are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate lobomarinopython if I installed it?

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

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

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

Malicious package

lobomarinopythonPyPI

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

MAL-2024-12300

Immediate action

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

pip uninstall lobomarinopython

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.0.0

Indicators of compromise (SHA-256)

e679c009b857de3d3924966368d135cd47e89d8be9f68e691dcadd81e3a55bd1

abf82fb6ceeaa4bb5cb2b1198b74e02f2f19c2d65b18dcd025000fcaddfc4228

db4087c089f3b78e5397076fec87d8ae2f03b1dc45cb5d8a202abf04728575ba

8c88a70b836849d98530b269952c9dbb0bd80e286605037fee38740a0263ff5f

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