selfsigned-certificate
Generates random self-signed SSL certificates in memory for development and testing
This report shows the evidence for selfsigned-certificate@1.0.0. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis package contains a concrete, user-triggered remote code execution chain hidden inside its certificate generator. The behavior is unrelated to its stated purpose and warrants blocking.
Decision evidence
public snapshot- The exported API has a hidden count-specific path that contacts a remote server.
- The remote response is Base64-decoded and passed directly to eval.
- Remote code execution is unrelated to generating self-signed certificates and is not documented.
- package.json contains no lifecycle scripts.
- The normal certificate-generation path uses the declared selfsigned dependency in memory.
Source & flagged code
6 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
index.jsView on unpkg · L36The exported API has a hidden count-specific path that contacts a remote server.
index.jsView on unpkg · L37The remote response is Base64-decoded and passed directly to eval.
index.jsView on unpkg · L110Findings
Affected versions and remediation
This report applies to selfsigned-certificate@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing selfsigned-certificate@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.