Which versions of selfsigned-certificate are malicious?

The following npm versions of selfsigned-certificate are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate selfsigned-certificate if I installed it?

selfsigned-certificate is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed selfsigned-certificate — how do I know if it already compromised me?

If selfsigned-certificate was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is selfsigned-certificate part of a known attack campaign?

Yes — selfsigned-certificate is associated with the GHSA-3whj-3fjw-x5w8, IN-MAL-2026-019335, IN-MAL-2026-019336 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find selfsigned-certificate across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for selfsigned-certificate (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging selfsigned-certificate across your stack and pipelines.

Malicious package

selfsigned-certificatenpm

selfsigned-certificate is a confirmed malicious npm package (MAL-2026-15623) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in selfsigned-certificate (npm)

MAL-2026-15623

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall selfsigned-certificate

What this malware does

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.

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.

Malicious versions

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

9c9b5302e4aa70efecf100380640080ec5cdfdf1fc983c95ee499303f76c1fcc

26324f10054a4b02e6d50af8f5373115e113a01c37d636ed70df2be1dd1b6b92

d79dd849caa5de3d6f0df51f8591b3157c46a2fd1fae8f7b28dc68a8a5cb05a4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for selfsigned-certificate (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging selfsigned-certificate across your stack and pipelines.
If you installed it — respond
selfsigned-certificate is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If selfsigned-certificate was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks selfsigned-certificate before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. selfsigned-certificate on npm has been identified as a malicious package (versions 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3whj-3fjw-x5w8IN-MAL-2026-019335IN-MAL-2026-019336

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks selfsigned-certificate-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database