PyPI: 8 Typosquats Impersonating 'semver' Disclosed in 11-Minute Burst
On October 20, 2026, ten malicious packages, including eight typosquats targeting the popular `semver` library, were disclosed on PyPI within an 11-minute window, indicating a coordinated campaign.

Key findings
- Ten malicious packages were disclosed on PyPI within an 11-minute window on October 20, 2026.
- Eight of the packages were typosquats targeting the popular
semverlibrary. - Affected package names include
semverr,semvver,semveer, andsemmver. - All disclosed advisories indicated Critical severity for the malicious versions.
Coordinated PyPI Typosquat Campaign Targets semver
On October 20, 2026, ten malicious packages were disclosed on the Python Package Index (PyPI) within a tight 11-minute window, from 18:20 UTC to 18:31 UTC. This rapid succession of disclosures indicates a coordinated campaign, primarily characterized by typosquatting attacks against the widely used semver library. The burst included eight distinct packages designed to impersonate semver, alongside two other packages with names suggesting security research themes.
The core of this coordinated effort involved a series of typosquats targeting semver, a popular library for semantic versioning. Attackers published variations of the legitimate package name, likely hoping to trick developers into inadvertently installing malicious code due to common typing errors or automated dependency resolution. Examples of these deceptive package names include semverr, semvver, semveer, and semmver. Each of these typosquat packages appeared multiple times in the disclosure list, reinforcing the coordinated nature of their release. Additionally, two other packages, research-probe-6150c1c915 and security-research-startup-snapshot-810764b303, were part of the same disclosure window, suggesting they may be related components of the same malicious operation or an attempt to blend in with legitimate security research activities.
Severity and Impact
The advisories for all disclosed packages uniformly assigned a Critical severity rating. This classification typically indicates that any system installing such a package should be considered fully compromised, requiring immediate and thorough remediation steps. While specific details regarding the malicious payloads or their exact behavioral characteristics were not publicly detailed in the advisories, the critical severity implies that these packages could perform a range of harmful actions, from data exfiltration and credential theft to establishing persistent backdoors on affected systems. Users are strongly advised to treat any machine that installed these packages as untrusted, rotating all credentials and secrets from a separate, secure environment.
Detection and Response
Developers should immediately audit their project dependencies to identify any installations of these malicious packages. It is crucial to check requirements.txt, Pipfile.lock, or pyproject.toml files for direct or transitive dependencies on the following names:
semverrsemvversemveersemmverresearch-probe-6150c1c915security-research-startup-snapshot-810764b303
If any of these packages are found, they should be immediately removed, and a comprehensive security audit of the affected environment should be performed. Given the critical severity, all credentials, API keys, and sensitive data accessible from the compromised system must be considered compromised and rotated.
Broader Context
This burst of malicious packages underscores the persistent threat of typosquatting and coordinated attacks targeting open-source package registries like PyPI. Attackers frequently leverage subtle naming variations to exploit human error and automated build processes, aiming to inject malicious code into software supply chains. The rapid, coordinated disclosure of these packages highlights the ongoing efforts by security researchers and registry maintainers to detect and remove such threats, but also serves as a reminder for developers to maintain vigilance and employ robust dependency verification practices.