PyPI

The pingdomv3 PyPI Revival Hijack

Updated 5 Oct 2026 · Incident date 12 Apr 2024

pingdomv3 1.0.1 on PyPI, published by a new owner after the name was released, ran remote code during Jenkins builds in April 2024.

The last clean release, 0.0.6, came out in April 2020. The sources are JFrog, BleepingComputer and The Hacker News.

What happened

An attacker re-registered a deleted package name and published new releases under it. JFrog calls this Revival Hijack. Pip shows no warning for such an upgrade.

  • November 2019: the original author, cheneyyan, publishes version 0.0.2.
  • April 2020: last legitimate release, 0.0.6.
  • 27 March 2024: version 0.1 is a deprecation notice.
  • 30 March 2024: the author deletes the project. An account named Jinnis takes the name and publishes version 1.0.0.
  • 12 April 2024: JFrog detects a version with the payload.

The payload checks for the JENKINS_URL environment variable. If it is present, it fetches Python code from https://yyds.yyzs.workers.dev/meta/statistics and runs it with exec().

Affected versions

  • Clean: pingdomv3 0.0.6 and earlier, from the original owner.
  • Malicious: every release the new owner published after 30 March 2024, starting at 1.0.0. The record lists 1.0.1 as the version with the payload.
  • The sources list no fixed release.

Indicators of compromise

  • Domain: yyds.yyzs.workers.dev, path /meta/statistics.
  • Code that reads JENKINS_URL and then calls exec() on content from a remote server.
  • Package author changed from the original owner to a new account (Jinnis).
  • Installed version above 0.0.6.

How to check

Check the installed version and the author on every build host.

pip show pingdomv3

Search your Python environments for the domain.

grep -rl "yyds.yyzs.workers.dev" $(python3 -c "import site;print(site.getsitepackages()[0])")

What to do now

  1. Remove pingdomv3 from your requirements and uninstall it from build images.
  2. If a Jenkins job installed a release above 0.0.6, treat that agent as exposed. Rotate the credentials that the job can read.
  3. Pin dependencies to exact versions and use hash checking.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `pingdomv3` 0.0.6. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

pingdomv3 0.0.6

A revived, previously abandoned monitoring helper gained hidden code that fetched and ran commands from a stranger's website during builds.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

What is a Revival Hijack?

Someone registers the name of a deleted PyPI package and publishes new releases under it. Pip treats the new release as a normal update.

What did the pingdomv3 malware do?

In a Jenkins build, it fetched Python code from a remote site and ran it with exec().

Sources

  1. jfrog.com/blog/revival-hijack-pypi-hijack-technique-exploited-22k-packages-at-risk/
  2. bleepingcomputer.com/news/security/revival-hijack-supply-chain-attack-threatens-22-000-pypi-packages/
  3. thehackernews.com/2024/09/hackers-hijack-22000-removed-pypi.html

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library