0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
fetch-hash-cache-atomic
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting fetch-hash-cache-atomic, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-18340 | Unknown | Malicious code in fetch-hash-cache-atomic (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7fa5c13f5b907c79079d9030292f1a6dac9d2f0ced56c2efe0e1bfd7021acdb4) package.json declares its sole dependency as a direct HTTPS URL (https://artifacts.creditslib.com/npm/plugin-client-queue-field) rather than a registry version range, with no version pin and no integrity hash. On npm install, npm fetches whatever bytes that URL currently returns and installs them, executing any lifecycle scripts the fetched tarball contains. The shipped index.js is a one-line re-export of that dependency, so the manifest li |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7fa5c13f5b907c79079d9030292f1a6dac9d2f0ced56c2efe0e1bfd7021acdb4) package.json declares its sole dependency as a direct HTTPS URL (https://artifacts.creditslib.com/npm/plugin-client-queue-field) rather than a registry version range, with no version pin and no integrity hash. On npm install, npm fetches whatever bytes that URL currently returns and installs them, executing any lifecycle scripts the fetched tarball contains. The shipped index.js is a one-line re-export of that dependency, so the manifest li