Which versions of yelp-pkg are malicious?

The following PyPI versions of yelp-pkg are flagged malicious: 1337.0.0. Treat any of these as compromised.

How do I remediate yelp-pkg if I installed it?

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

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

Yes — yelp-pkg is associated with the RLMA-2025-05644, GENERIC-questionable-pentest, RLUA-2026-00940 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 yelp-pkg 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 yelp-pkg (version 1337.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yelp-pkg across your stack and pipelines.

Malicious package

yelp-pkgPyPI

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

MAL-2025-191666

Immediate action

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

pip uninstall yelp-pkg

What this malware does

During import, the package attempts to exfiltrate potentially sensitive data.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

1 flagged

1337.0.0

Indicators of compromise (SHA-256)

6c7a1648bff6faa98675b02278353e85594405df04fe9bbd92cf3f1151ce79e0

70b3149ccd32bf7e90a06b289e8ea3363279bbe38f6047eb5427e04a12fc11d1

fdea5ca17bb09234a292159e525a2a38ac3fd43760c6f2184aa27f563f320075

73eab611641522ed8e570f6dc66743eb01811ab883fa2aa94db61e5c7a2c79e2

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

Campaign

RLMA-2025-05644GENERIC-questionable-pentestRLUA-2026-00940

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks yelp-pkg-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