pyyi has 1 compromised version.

HighAdvisory sweepPyPI

pyyi has 1 version on PyPI flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories. pyyi was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Check my requirements.txt What to do

At a glancePyPI

Compromised versionDo not install these

If one is in your tree, treat the machine as compromised, not just out of date.

Ecosystem: PyPI
Worst severity: High
Incidents: 1
First flagged: 14 Oct 2026
Type: Advisory sweep

Version data comes from the public advisories cited on each incident page.

Affected versions

The exact releases to look for.

Check what you actually have installed with pip show pyyi.

pyyi@2.4.1

The incident

The incident that flagged it

HighAdvisory sweep14 Oct 2026

GitHub Advisory malware sweep, 14 October 2026

GHSA 2026-10-13/14 batch (~21 fresh malware advisories). Headliner: orderly-plugin-liquidity-heatmap abuses the installers GitHub Actions GITHUB_TOKEN to commit heatmap-setup-report.json and force-push a heatmap-setup-<timestamp> tag into the victims own repository. Confirmed-payload carve-outs: PyPI fontcase infostealer + Telegram bot, PyPI sysdiagd Discord RAT, PyPI pyyi python2 impersonator, npm Accenture-brand dep-confusion with azurewebsites.net C2, npm passwordcracker continuing limbomail.com, plus a 10-slug opencode2* typosquat of @opencode-ai/cli.

Versions named here: 2.4.1Read the incident →

What to do

Installed one of these? Start here.

Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

Rotate every credential that machine or CI job could reach, such as registry tokens, cloud keys, SSH keys and CI secrets, from a different machine.
Pin to a version not listed above, then reinstall from a clean lockfile.
Clear caches and private mirrors. Artifactory, Nexus, Verdaccio and devpi routinely keep serving a tarball after the public registry has pulled it.
Read the incident write-up. Recommended actions differ per incident, and some have specific indicators of compromise worth searching your logs for.

Same campaign

Other packages in the same incident

If pyyi is in your tree, these are worth checking too. They were published by the same campaign.

See the full incident →All flagged PyPI packages →

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.

Check your whole project

Check every dependency, not just this one.

It is usually pulled in as a transitive dependency rather than one you installed directly. Paste your requirements.txt to check every dependency at once. It runs in your browser and nothing is uploaded.

Check my requirements.txt All PyPI packages