Threats Tagged 'mal-2026-15510'
View all threats tagged with 'mal-2026-15510'. 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-15510'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in integration-amplitude (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (dcd9ffdf0c07f64af4034ec76aea284a6290f4633f2c80eefa65579c1a297bfb) package.json declares the package's own name as a dependency whose source is the bare HTTPS URL https://repo.securityctrl.com/integration-amplitude rather than a registry version range. On npm install, npm fetches whatever bytes that host serves and installs them, executing any lifecycle scripts contained inside, with no version pin and no integrity check. The shipped index.js is a 3-line stub, so this manifest line is the sole install-time code path. The dependency key matching the package's own name is the dependency-confusion shape, and the implausibly high version (45.0.0) is consistent with an attempt to win resolution against an internal package of the same name. Whoever controls repo.securityctrl.com controls code executed on the installer's machine. Join the discussion | GCVE Database | 08/28/2026, 23:12:22 UTC Added: 08/29/2026, 15:16:51 UTC |
Showing 1 to 1 of 1 result