The incidents behind a package’s reputation. Read what happened, which releases were affected, and what the original investigators found.
Reviewed reports · last reviewed 2026-09-05. This is a selected incident record, not an exhaustive live threat feed. A past compromise does not establish that the current release is compromised.
Wiz reported that hijacked releases added a malicious dependency that ran during compilation. Rust responders removed those releases. Wiz also identified infrastructure shared with previously reported DPRK-linked campaigns.
Wiz documented malicious releases following a maintainer account compromise. The payload targeted developer and cloud credentials and attempted to spread through package publishing.
StepSecurity traced two malicious Axios releases to compromised publishing credentials. A newly added dependency delivered the payload; the affected releases were subsequently removed from npm.
JFrog documented backdoored PyPI releases after a compromised Trivy build tool exposed publishing credentials. The report describes credential theft and the project’s change to a pinned Trivy version.
Aikido reported compromised releases across a widely used group of npm packages. The injected browser code attempted to redirect cryptocurrency transactions to attacker-controlled destinations.
Affected versions: Affected releases differ by package; see the original report.
Nx described how a GitHub Actions injection exposed a publishing token and enabled malicious releases that collected sensitive files. Its response included trusted publishing and manual release approval.
Affected versions: See Nx’s linked advisory for the package-specific affected versions.
High-profile vulnerabilities and your dependencies
Astra’s top-ten article ↗ collects historical CVEs from 2020–2022. It is not a live ranking or the OWASP Top 10. The mapping below explains which entries relate to package identities we check.
An identity match is a reason to investigate, not confirmation that your installed release is vulnerable. Manifest checks do not establish runtime configuration or resolve every transitive dependency.
Requires Windows and domain configuration assessment.
Outside package-only scan coverage
Runtime vulnerabilities on OpenCVE
Browse CVEs by vendor and product. Runtime CVEs do not automatically apply to every package in that ecosystem; verify affected versions and configurations.
Follow these publishers and official advisories for broader coverage. RSS links open their feeds; articles are not automatically imported into the reviewed reports above. Feedspot is a directory for discovering feeds.