Which versions of noverojava are malicious?

The following npm versions of noverojava are flagged malicious: 1.0.9, 1.1.0. Treat any of these as compromised.

How do I remediate noverojava if I installed it?

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

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

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

Malicious package

noverojavanpm

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

Malicious code in noverojava (npm)

MAL-2026-16389

Immediate action

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

npm uninstall noverojava

What this malware does

package.json declares the runtime dependency libsignal as github:tenka-san/libsignal-node rather than a registry version range or pinned commit SHA. On npm install, npm fetches the current HEAD of that fork's default branch and executes any lifecycle scripts it defines. The fork is under a third-party GitHub account (not the upstream WhiskeySockets libsignal-node maintainer), has no commit pin, and no integrity check, so whoever controls that account controls code that runs on the installer's machine at install time. The package presents as a Baileys/WhatsApp library fork; the static match on lib/Utils/generics.js line 403 (ping/GET tokens) is consistent with normal Baileys network code and is not independently indicative of exfiltration.

Malicious versions

2 flagged

1.0.91.1.0

Indicators of compromise (SHA-256)

4d712fbfd1c2e69c89e7f8f00bfe47b097f18e5b1b603f8d1eb505e70dc80ba0

a7fbf0d1519b05868b34e9e2c1d3588a0596003a5cb53e4cd28fd3a856ecff26

ddf2122800252802a165ef37901259d97574d8e2f00d3f7c354fac24f2ead971

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

Campaign

IN-MAL-2026-020297IN-MAL-2026-020299IN-MAL-2026-020296

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks noverojava-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