HighPyPI11 affected versions

infogram-bot

infogram-bot has 11 versions on PyPI flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with pip show infogram-bot.

infogram-bot@1.9.0
infogram-bot@1.8.0
infogram-bot@1.7.0
infogram-bot@1.6.1
infogram-bot@1.6.0
infogram-bot@1.5.0
infogram-bot@1.4.0
infogram-bot@1.3.0
infogram-bot@1.2.1
infogram-bot@1.2.0
infogram-bot@1.0.0

The incident that flagged it

High18 Aug 2026

GitHub Advisory malware sweep - 2026-08-17 / 2026-08-18 batch (Sui blockchain `@mysten/*` typosquat days 4-5 continuation `sui-move-graphql`+`sui-move-rpc`+`sui-gql-core`+`bcs-core`+`bucket-protocol-sdk-v2`, Tinkoff BNPL dep-confusion tail `bnpl-blocks-independent-bnpl-search`, LEB128 encoding typosquat pair `leb128x`+`ulebkit`, generic CWE-506 boilerplate `blastradar`+`runtime-health`, PyPI Telegram-RAT trio `socks5901`+`infogram-bot`+`httpz-requests`)

13 GHSA CWE-506 advisories across npm + PyPI in the 24h ending 2026-08-18 06:00 UTC (extended 2026-08-19 with two late PyPI Telegram-RAT entries). Headline: five-package Sui blockchain typosquat continuation (sui-move-graphql, sui-move-rpc, sui-gql-core, bcs-core, bucket-protocol-sdk-v2) extends the @mysten/* typosquat register into day-4/5. Also: Tinkoff BNPL dep-confusion tail, leb128x+ulebkit LEB128 typosquat pair, generic CWE-506 pair, and a PyPI Telegram-RAT trio socks5901+infogram-bot+httpz-requests.

Versions named here: 1.0.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.6.1, 1.7.0, 1.8.0, 1.9.0

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

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

Check your whole project

infogram-bot is one of many packages in these incidents, and 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 flagged PyPI packages

Other packages in the same incident

If infogram-bot is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.