0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
aws-blog
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 aws-blog, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-15498 | Unknown | Malicious code in aws-blog (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b036991e88a4be9813e89ba9861b39ae37fbd9201d1bd017f81c8b33d5f5e44b) package.json declares a dependency whose key equals the package's own name (`aws-blog`) with a value of `https://repo.securityctrl.com/aws-blog` instead of a registry version range. On `npm install`, npm fetches whatever tarball bytes that URL currently returns and installs it, running any lifecycle scripts inside it. There is no version pin and no integrity hash, so the executed code is whatever the operator of repo.securityctrl.com serves |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b036991e88a4be9813e89ba9861b39ae37fbd9201d1bd017f81c8b33d5f5e44b) package.json declares a dependency whose key equals the package's own name (`aws-blog`) with a value of `https://repo.securityctrl.com/aws-blog` instead of a registry version range. On `npm install`, npm fetches whatever tarball bytes that URL currently returns and installs it, running any lifecycle scripts inside it. There is no version pin and no integrity hash, so the executed code is whatever the operator of repo.securityctrl.com serves