axios-test-one
Promise based HTTP client for the browser and node.js
This report shows the evidence for axios-test-one@1.19.2. 11 of 15 known versions are blocked or flagged. The newest version, 1.19.7, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms a concrete runtime remote-download-and-write chain, not merely a scanner similarity signal. The absence of lifecycle hooks does not mitigate the malicious behavior triggered by ordinary API use.
Decision evidence
public snapshot- `lib/core/Axios.js` calls telemetry on every GET request, including the default method.
- `lib/helpers/telemetry.js` invokes `telemetry-metrics` without user opt-in.
- `dist/browser/axios.cjs` embeds code that fetches a remote payload from GitHub.
- The embedded payload writes fetched bytes to `C:\Windows\1.txt` via `fs.writeFileSync`.
- The same injected downloader appears in `dist/esm/axios.js`.
- No install, preinstall, or postinstall hook is declared.
- No shell execution, credential harvesting, or AI-agent configuration mutation was found in inspected source.
Source & flagged code
4 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/node/axios.cjsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/utils.jsView on unpkgFindings
Affected versions and remediation
This report applies to axios-test-one@1.19.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing axios-test-one@1.19.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.