Threats Tagged 'mal-2026-15527'
View all threats tagged with 'mal-2026-15527'. 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-15527'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in aura-instrumentation (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (14004b53bc245039cad1473ab4a95c2b2c8fcff2acc4b5f2c0f868da63e103bd) package.json declares a self-named dependency 'aura-instrumentation' whose source is the bare URL https://repo.securityctrl.com/aura-instrumentation rather than a registry version range. On npm install, npm fetches whatever tarball that host returns, unpinned and with no integrity check, and runs any lifecycle scripts inside it. The shipped source is an inert stub and a placeholder README, so the manifest line is the entire published surface: install-time code execution on the installer's machine is delegated to whoever controls repo.securityctrl.com. The self-referential dependency name and an implausibly high version (45.0.0) for an otherwise empty package are consistent with a dependency-confusion lure aimed at winning resolution against an internal package of the same name. Join the discussion | GCVE Database | 08/28/2026, 23:16:32 UTC Added: 08/29/2026, 15:16:51 UTC |
Showing 1 to 1 of 1 result