selfcerts@1.0.0

index.js reads sample/cert.pem, strips the BEGIN/END CERTIFICATE header and footer, base64-decodes the body, and eval()s the result. The decoded bytes are a JavaScript IIFE that base64-decodes a hardcoded URL (http://144.172.104.211/settings/privacy.php), fetches its response over plain HTTP, and pipes the body into a detached python3 process via stdin, executing whatever the remote host returns. The loader (loadSampleCertificate) is invoked unconditionally at the top of the exported generateCertificates() API, so any consumer that uses the package as advertised triggers remote code execution on the installer's host. Presenting an executable payload as a PEM certificate and nesting the C2 URL under a second base64 layer is deliberate obfuscation with no legitimate role in a certificate-generation library.