Your RSA-2048 keys break in 2030. Find every one of them before attackers do.See CBOMkit
2025-06-atlasctf
The 2025-06-atlasctf campaign published 23 malicious PyPI packages. See the full package list, timeline, and how to check whether your dependency tree pulled any of them in.
Malicious packages
23
Advisories
23
Ecosystem
PyPI
First seen
2025-06-07
What to do if you depend on any of these
Every package below was published as malicious under 2025-06-atlasctf. Treat any machine that installed one as compromised: remove the package and its lockfile entry, rotate every credential the build or runtime could reach (registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values) from a known-clean machine, and audit for unexpected outbound activity.
Because the packages share a campaign, a project that pulled in one has an elevated chance of having pulled in others. Search your lockfiles for 2025-06-atlasctf rather than checking a single package name.
All 23 packagesPyPI
- atlasctf-21-prod-00View advisory →
- atlasctf-21-prod-01View advisory →
- atlasctf-21-prod-02View advisory →
- atlasctf-21-prod-03View advisory →
- atlasctf-21-prod-04View advisory →
- atlasctf-21-prod-05View advisory →
- atlasctf-21-prod-06View advisory →
- atlasctf-21-prod-07View advisory →
- atlasctf-21-prod-08View advisory →
- atlasctf-21-prod-09View advisory →
- atlasctf-21-prod-10View advisory →
- atlasctf-21-prod-11View advisory →
- atlasctf-21-prod-12View advisory →
- atlasctf-21-prod-13View advisory →
- atlasctf-21-prod-14View advisory →
- atlasctf-21-prod-15View advisory →
- atlasctf-21-prod-16View advisory →
- atlasctf-21-prod-17View advisory →
- atlasctf-21-prod-18View advisory →
- atlasctf-21-prod-19View advisory →
- atlasctf-21-prod-20View advisory →
- atlasctf-21-prod-21View advisory →
- atlasctf-21-prod-29View advisory →