Which versions of javas-crypto are malicious?

The following npm versions of javas-crypto are flagged malicious: 2.0.4. Treat any of these as compromised.

How do I remediate javas-crypto if I installed it?

javas-crypto 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 javas-crypto — how do I know if it already compromised me?

If javas-crypto 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 javas-crypto part of a known attack campaign?

Yes — javas-crypto is associated with the IN-MAL-2026-015798 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 javas-crypto 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 javas-crypto (version 2.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging javas-crypto across your stack and pipelines.

Malicious package

javas-cryptonpm

javas-crypto is a confirmed malicious npm package (MAL-2026-13347) that steals credentials and exfiltrates sensitive data (malicious version 2.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in javas-crypto (npm)

MAL-2026-13347

Immediate action

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

npm uninstall javas-crypto

What this malware does

javas-crypto ships a postinstall hook (package.json line 11: "postinstall": "node setup.js") and a top-level autoExecute() in index.js that both enumerate the full process.env (minus a small shell-variable allowlist) and POST every captured key=value pair, along with hostname and CI job/project/commit identifiers, to an HTTP backend read from environment variables, package.json,.crypto-config.json, or.env. In the advertised CI/CD context, process.env contains credentials such as AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, GITLAB_TOKEN, and registry publish tokens, all of which are transmitted in plaintext form to the configured endpoint. The exfiltration path fires automatically on npm install (via the postinstall hook) and again on any require/import of the package. Package metadata frames the behavior as a "Secure environment variable handler for GitLab CI/CD pipelines" by author "DevSecOps" with placeholder repository gitlab.com/example/js-crypto.git, and the package name javas-crypto resembles js-crypto. Function names such as SecretsHandler, sendToBackend, and formatPayload present bulk secret harvesting as a security feature. Errors during transmission are silently swallowed so the victim sees no failure.

Malicious versions

1 flagged

2.0.4

Indicators of compromise (SHA-256)

eb8d6c5cf1104be2efdc1b3e6ff2e6dbc19f8b5036f87f6edaf99116216c0c53

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 javas-crypto (version 2.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging javas-crypto across your stack and pipelines.
If you installed it — respond
javas-crypto 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 javas-crypto 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 javas-crypto 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. javas-crypto on npm has been identified as a malicious package (version 2.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015798

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks javas-crypto-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