Malicious PyPI package backdoors installs via remote code download
TL;DR — The photo-extractor package on PyPI was flagged as malicious and designed to pull and run remote payloads, creating a supply-chain backdoor risk for any environment that installed it.
What happened
photo-extractor is a Python package distributed via PyPI. OSV has published MAL-2026-2488 classifying photo-extractor as MALICIOUS, describing it as a clone of a legitimate library with malicious modifications intended to download and execute remote code.
Per the OSV record, the remote script "allows executing arbitrary files" using Telegram as a C2 channel, and the package installs a generic entry point that triggers the malicious behavior.
This is operationally high risk because malicious package releases frequently land via routine dependency updates (CI builds, container rebuilds, developer installs) and can exfiltrate secrets or establish persistence before detection.
Who is impacted
- Any environment that installed
photo-extractorfrom PyPI, particularly version2.33.0(the version explicitly listed in the OSV "origins" metadata). - CI/CD runners, developer workstations, and production build systems that allow outbound network access during dependency installation.
| Item | Source value |
|---|---|
| Ecosystem / package | PyPI photo-extractor |
| Malicious version called out | 2.33.0 |
| OSV classification | MALICIOUS |
| OSV published timestamp | 2026-04-04T16:41:48Z |
| Reported behavior | Downloads and executes a remote script; Telegram used as C2 |
| Reported URLs (IOCs) | https://tinyurl.com/47h5bmcw, https://www.dropbox.com/.../shadowsocksvpn.ps1?...&dl=1 |
What to do now
- Inventory and remove
photo-extractorfrom dependency manifests/lockfiles and identify any installations of version2.33.0across dev, CI, and production build environments. - If you confirm installation/execution, treat affected hosts and credentials as potentially compromised:
- Rotate secrets accessible to the impacted runtime (CI tokens, cloud keys, deployment credentials).
- Review egress/network telemetry for suspicious outbound connections around install time.
- Add detections for the reported URLs/IOCs from the OSV record in proxy/DNS logs and endpoint telemetry.
- For future resilience, tighten dependency ingestion controls (pinned lockfiles, allowlisted registries, and reduced/controlled install-time network egress in CI).
Content is AI-assisted and reviewed by our team, but issues may be missed and best practices evolve rapidly, send corrections to [email protected]. Always consult official documentation and validate key implementation decisions before making design or security choices.