Malicious code in self-sign (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-14544
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b684f78f17626dead6b3d11131179a7a1aff7fa5e903daeecdac17ce8e3b99b3) The exported generate() function in [email protected] accepts an undocumented third `defaults` parameter. When passed a string, the code strips PEM `-----BEGIN CERTIFICATE-----` headers, base64-decodes the remaining body, and passes the result to eval() inside a silent try/catch. The TypeScript declaration file advertises only two parameters, concealing the sink, while the shipped README examples pass a third argument (null), normalising the call shape so downstream callers can be induced to propagate attacker-controllable certificate-shaped strings into the eval sink. A cryptographic/x509 helper has no legitimate reason to evaluate base64 content extracted from a certificate string; this pattern yields arbitrary JavaScript execution in the process of any consumer that reaches this code path with attacker-influenced input. The package.json name (`self-sign`) also diverges from the require identifier used in the shipped documentation (`require('selfsign')`), a naming inconsistency that supports confusion with the legitimate selfsigned library. ## Source: ghsa-malware (b8adbf388bace10b905f93be8487c3b1866d941ecc0f968972de85f3b20f44de) 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
- 27 Aug 2026 04:00:13 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.