Which versions of iufgbewroibgfowiebc are malicious?

The following PyPI versions of iufgbewroibgfowiebc are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate iufgbewroibgfowiebc if I installed it?

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

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

Yes — iufgbewroibgfowiebc is associated with the 2024-10-lokopoil23 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 iufgbewroibgfowiebc 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 iufgbewroibgfowiebc (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iufgbewroibgfowiebc across your stack and pipelines.

Malicious package

iufgbewroibgfowiebcPyPI

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

MAL-2024-9306

Immediate action

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

pip uninstall iufgbewroibgfowiebc

What this malware does

According to the description, packages should demonstrate the dependency confusion attack. The realisation is, in fact, a spamming with packages having as the only purpose reporting basic data like hostname and current working directory.

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-10-lokopoil23

Reasons (based on the campaign):

dependency-confusion

The OpenSSF Package Analysis project identified 'iufgbewroibgfowiebc' @ 0.0.2 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

c2b2b09ca0baae5d76aae6930f72f167ac70938e3cf7f95a2372133bd49ddbeb

b8e3ff85c394d4f8c08b22c007ca1030388be4139a505b44e59b5228f679a356

06029514a813cf9b228f1be7c997bffc2510869a5f0130d6036fa63ee6ea2fbc

49360ba1adc73fb91d4e78db770d408f657fd5a1d4ae0bfd4b2a7f4148b4782c

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

Campaign

2024-10-lokopoil23

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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