Which versions of jz-native-js-bridge are malicious?

The following npm versions of jz-native-js-bridge are flagged malicious: 114.5.14. Treat any of these as compromised.

How do I remediate jz-native-js-bridge if I installed it?

Remove jz-native-js-bridge 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 jz-native-js-bridge — how do I know if it already compromised me?

If jz-native-js-bridge 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 jz-native-js-bridge part of a known attack campaign?

Yes — jz-native-js-bridge is associated with the RLMA-2025-06383 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 jz-native-js-bridge across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jz-native-js-bridge (version 114.5.14).

Malicious package

jz-native-js-bridgenpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

jz-native-js-bridge is a confirmed malicious npm package (MAL-2025-192817) that executes malicious code on install (malicious version 114.5.14). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jz-native-js-bridge (npm)

MAL-2025-192817

Immediate action

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

npm uninstall jz-native-js-bridge

What this malware does

The package jz-native-js-bridge was found to contain malicious code.

Malicious versions

1 flagged

114.5.14

Indicators of compromise (SHA-256)

ee57d8bcf4e4e447f0b30d39a1fcc672e0e62f94a16fdadc59d1bcc0c37b1e15

8f5be9f16b75f7bf0ca5477443252a99142fcc146e923a7f77862df124ad6ac5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for jz-native-js-bridge (version 114.5.14).
If you installed it — respond
Remove jz-native-js-bridge 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 jz-native-js-bridge 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. jz-native-js-bridge on npm has been identified as a malicious package (version 114.5.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06383

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks jz-native-js-bridge-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