self-sign
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting self-sign, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-14544 | Unknown | Malicious code in self-sign (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b684f78f17626dead6b3d11131179a7a1aff7fa5e903daeecdac17ce8e3b99b3) The exported generate() function in self-sign@5.6.7 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 |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b684f78f17626dead6b3d11131179a7a1aff7fa5e903daeecdac17ce8e3b99b3) The exported generate() function in self-sign@5.6.7 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