Threats Tagged 'mal-2026-15498'
View all threats tagged with 'mal-2026-15498'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'mal-2026-15498'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in aws-blog (npm) 0 --- _-= 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 at install time and can change silently between installs. The shipped source is an inert stub, so the manifest line is the entire published surface of the package. The dependency-confusion shape (self-named key, implausibly high 45.0.0 version to win resolution against an internal `aws-blog`, host unrelated to any AWS or npm infrastructure) further indicates targeting of installers who expect an internal package by this name. Join the discussion | GCVE Database | 08/28/2026, 23:12:05 UTC Added: 08/29/2026, 15:16:50 UTC |
Showing 1 to 1 of 1 result