Which versions of mylib-utils are malicious?

The following PyPI versions of mylib-utils are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate mylib-utils if I installed it?

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

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

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

Malicious package

mylib-utilsPyPI

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

MAL-2026-2860

Immediate action

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

pip uninstall mylib-utils

What this malware does

During import, a remote executable is automatically started. During analysis, the executable only showed a basic message. It's likely experimenting with malicious techniques to prepare for real malicious action.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-04-mylib-utils

Reasons (based on the campaign):

Downloads and executes a remote executable.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

8cc746751844570c4d9de0acc1fc4aba45c1316434c664fc70711749720f88f1

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

Campaign

2026-04-mylib-utils

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks mylib-utils-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