Threats Tagged 'mal-2026-15497'
View all threats tagged with 'mal-2026-15497'. 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-15497'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in amplitude-session-replay (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fb71ca2dc9e74e42a64b1533ecb98ea1cad26e283b0c3d3ba0f4e7c760fac713) package.json declares a dependency whose key is the package's own name (`amplitude-session-replay`) and whose value is a plain HTTPS URL, `https://repo.securityctrl.com/amplitude-session-replay`, instead of a registry version range. On `npm install`, npm fetches the tarball bytes returned by that URL and installs whatever it contains, including running any lifecycle scripts inside — with no version pin, no integrity hash, and no registry vetting. The shipped source in the published tarball is an inert stub, so the manifest itself is the delivery mechanism: whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency name (dependency-confusion shape) also encourages resolvers to prefer this entry over any legitimately-named `amplitude-session-replay` package. The host is unrelated to Amplitude's own domains. Join the discussion | GCVE Database | 08/28/2026, 23:12:29 UTC Added: 08/29/2026, 15:16:51 UTC |
Showing 1 to 1 of 1 result