Threats Tagged 'mal-2026-15538'
View all threats tagged with 'mal-2026-15538'. 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-15538'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in librastandardlib (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (519c28eb8d9df0a16d93e1b1c486f1ad4a9092a9bf958aed56f273cfe1fcfc14) package.json at line 11 declares a dependency whose key equals the package's own name (librastandardlib) and whose value is an off-registry HTTPS URL (https://repo.securityctrl.com/librastandardlib) instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, running any lifecycle scripts inside with no version pin and no integrity check. The implausibly high version (45.0.0) and the self-referential dependency name are consistent with a dependency-confusion shape designed to win resolution against an internal package. The shipped index.js is an inert stub, so the manifest URL is the entire delivery mechanism — whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. Join the discussion | GCVE Database | 08/28/2026, 23:15:31 UTC Added: 08/29/2026, 15:16:51 UTC |
Showing 1 to 1 of 1 result