Malicious code in internallib_v514 (npm)
The npm package internallib_v514 contains malicious code that executes a reverse-shell payload by downloading and executing a shell script from a hardcoded internal IP address over plaintext HTTP. Any consumer invoking the exported `command` function executes attacker-controlled code with no integrity verification or TLS protection.
- Disclosed
- Last updated
- Blast radius
- Any consumer of internallib_v514 that invokes the exported `command` function
- Ecosystems
- Attack vectors
- Affected entities
- internallib_v514npm package containing malicious code in index.js
The npm package internallib_v514 was found to contain malicious code in its index.js file. The exported command function calls require('child_process').execSync() to synchronously download and execute a shell script from a hardcoded internal IP address (10.0.70.90) over plaintext HTTP.\n\nThe attack downloads a file named rev.sh from http://10.0.70.90/rev.sh and pipes it directly into sh for execution. The script name and behavior are consistent with a reverse-shell payload, indicating intent to establish unauthorized remote access.\n\nAny application that requires this package and invokes the exported function will execute the attacker-controlled code. The attack provides no integrity verification, no TLS encryption, and no certificate pinning, making it trivial for network-level attackers to intercept or modify the payload.\n\nThe incident was identified by the OpenSSF malicious-packages project and reported via GitHub Security Advisory GHSA-676x-3cvx-w3j5.
Indicators of compromise
- Packages
- internallib_v514
- IPs
- 10.0.70.90
Remediation
- Remove internallib_v514 from all dependencies immediately
- Audit all systems that may have installed or executed this package for signs of compromise or reverse-shell connections
- Review application logs for any invocations of the `command` function from this package
- Implement package integrity verification and code review processes for all npm dependencies
- Use npm audit and supply-chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-676x-3cvx-w3j5 · GitHub Advisory Database
Cite this entry
"Malicious code in internallib_v514 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-internallib-v514-npm-1iq0mp
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in epic-common (npm)
The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - containedcritical
Malware in @siwatfa/yorn
Malware was discovered in the npm package @siwatfa/yorn. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package - containedcritical
Malicious code in pfp-forms-sme-loan (npm)
The npm package pfp-forms-sme-loan contains malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under well1.site. Any system that imported this package should be considered compromised.
npmCompromised packageMalicious commit