Malicious code in @qwedqwed/axios (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-4422
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (65cc6ad7f5d72e7e50a4493915cc5b8ce23b39b6f25ca5515228be44695016ca) Package `@qwedqwed/axios` is published under a scope that does not belong to the real axios maintainers but copies axios's README, source, homepage (`axios-http.com`), repository (`github.com/axios/axios`), and author metadata (`Matt Zabriskie`) verbatim to present itself as the genuine axios library. Its `package.json` declares two runtime dependencies that the real axios does not use: `@caspianph/storyteller@^1.1.12` and `math@^0.0.3`. The `math` name is a long-abandoned npm utility frequently abused as a dependency-confusion / typosquat target, and `@caspianph/storyteller` is an unknown package under an unrelated scope. Installing or requiring `@qwedqwed/axios` resolves and loads both of those packages into the installer's dependency graph. The axios source bytes shipped in this tarball are themselves benign (the `ping` strings flagged are inside axios's normal HTTP adapter / utility code, not an exfil path), but the package functions as a lure: the harmful surface is the silently-pulled transitive code, not this tarball's own JavaScript. ## Source: ghsa-malware (b602128ba8b351ac4d372cf5e9eb8bcbd3523788f15850574bfbb0232ad05eb5) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 20 May 2026 07:04:14 UTC
- Source modified
- 14 Aug 2026 15:00:55 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.