Which versions of cdnjavacss are malicious?

The following npm versions of cdnjavacss are flagged malicious: 19.0.4. Treat any of these as compromised.

How do I remediate cdnjavacss if I installed it?

Remove cdnjavacss from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed cdnjavacss — how do I know if it already compromised me?

If cdnjavacss was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is cdnjavacss part of a known attack campaign?

Yes — cdnjavacss is associated with the RLMA-2026-01714 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 cdnjavacss across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cdnjavacss (version 19.0.4).

Malicious package

cdnjavacssnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

cdnjavacss is a confirmed malicious npm package (MAL-2026-2336) that executes malicious code on install (malicious version 19.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cdnjavacss (npm)

MAL-2026-2336

Immediate action

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

npm uninstall cdnjavacss

What this malware does

The package cdnjavacss was found to contain malicious code.

Malicious versions

1 flagged

19.0.4

Indicators of compromise (SHA-256)

5e44f556f1932af151743762a0a7b032446af4631aad78bbce5c801c3b08ae4c

1fb57ffd656f0a20fd4da4f7364cf96e67191700bda0682462b0ea9c68de1bb1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cdnjavacss (version 19.0.4).
If you installed it — respond
Remove cdnjavacss from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If cdnjavacss was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. cdnjavacss on npm has been identified as a malicious package (version 19.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01714

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks cdnjavacss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database