Threats Tagged 'mal-2026-15516'
View all threats tagged with 'mal-2026-15516'. 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-15516'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in nx-app (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8671a9b563cebe9de36365a80edc1f242be492933cadb3e45ea590c8c5e1e115) package.json declares its own name `nx-app` as a dependency whose value is a raw HTTPS URL (`https://repo.securityctrl.com/nx-app`) rather than a semver range against the npm registry. On `npm install`, npm fetches a tarball from that URL and runs any lifecycle scripts it contains, with no version pin, no integrity hash, and no signature check. Whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency key (matching the package's own name) is a dependency-confusion shape that forces resolution to the off-registry URL even when a registry-hosted `nx-app` exists, and the shipped in-tree source is an inert stub so the manifest URL is the sole payload delivery vector. Join the discussion | GCVE Database | 08/28/2026, 23:11:23 UTC Added: 08/29/2026, 15:16:51 UTC |
Showing 1 to 1 of 1 result