What does the lib-1779997093-yjeeqn malware do?

During installation, the package opens a reverse shell Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-05-my-test-package-2025-xyz Reasons (based on the campaign): - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine. - The package overrides the install command in setup.py to execute malicious code during installation.

Which versions of lib-1779997093-yjeeqn are malicious?

The following PyPI versions of lib-1779997093-yjeeqn are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate lib-1779997093-yjeeqn if I installed it?

lib-1779997093-yjeeqn 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 lib-1779997093-yjeeqn — how do I know if it already compromised me?

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

Yes — lib-1779997093-yjeeqn is associated with the 2026-05-my-test-package-2025-xyz 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 lib-1779997093-yjeeqn 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 lib-1779997093-yjeeqn (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 lib-1779997093-yjeeqn across your stack and pipelines.

Malicious package

lib-1779997093-yjeeqnPyPI

Malicious code in lib-1779997093-yjeeqn (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4861

Immediate action

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

pip uninstall lib-1779997093-yjeeqn

What this malware does

During installation, the package opens a reverse shell

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

Campaign: 2026-05-my-test-package-2025-xyz

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
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)

adfe3f8b85f731f407f8da6669a76b821b042e4ea1f2fd8fcfddf3293c2ca697

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 lib-1779997093-yjeeqn (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 lib-1779997093-yjeeqn across your stack and pipelines.
If you installed it — respond
lib-1779997093-yjeeqn 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 lib-1779997093-yjeeqn 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 lib-1779997093-yjeeqn 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. lib-1779997093-yjeeqn 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

2026-05-my-test-package-2025-xyz

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks lib-1779997093-yjeeqn-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