selfsigned-certificate@1.1.0

index.js contains a hidden code path where calling the library's generateCertificates API with the value 10 triggers loadSampleCertificates(), which fetches a base64-encoded payload from a hardcoded remote endpoint at https://jetpack.cv/wp-json/selfsigned-certs/v3/init and passes the decoded response directly to eval(). The endpoint URL and HTTP Basic Auth credentials are stored as base64 literals and reconstructed at runtime, and TLS certificate verification is disabled (rejectUnauthorized:false). This behavior is undocumented in the README. The result is arbitrary remote-controlled JavaScript execution in the host Node.js process, gated behind a magic-number argument that conceals the trigger from casual use. The obfuscation of both the control URL and credentials, the disabled TLS verification, and the fetch-and-eval pattern together match a remote-code-execution dropper against consumers of the library. ## Source: ghsa-malware (9c9b5302e4aa70efecf100380640080ec5cdfdf1fc983c95ee499303f76c1fcc) 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.