Threats Tagged 'mal-2026-15515'
View all threats tagged with 'mal-2026-15515'. 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-15515'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in npm-extension (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2a6c4f2b94932e8bcb68c0a146d536b7e3a00d48041aa5a6fc9edf9f82ae5244) package.json declares a dependency whose value is a bare HTTPS URL (https://repo.securityctrl.com/npm-extension) rather than a registry version range. On npm install, npm fetches whatever tarball that host returns and executes any lifecycle scripts inside it, unpinned and without integrity verification. The dependency key equals the package's own name, producing a dependency-confusion shape in which resolution is forced through the off-registry host. The shipped index.js is an inert stub, so the manifest line is the entire published payload — the fetched third-party code is what actually runs on installer machines. Join the discussion | GCVE Database | 08/28/2026, 23:12:49 UTC Added: 08/29/2026, 15:16:51 UTC |
Showing 1 to 1 of 1 result