Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

react-native-wm-barcodenpm

react-native-wm-barcode is a confirmed malicious npm package (MAL-2025-45765) that executes malicious code on install (malicious version 3.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in react-native-wm-barcode (npm)

MAL-2025-45765
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall react-native-wm-barcode

What this malware does

The package communicates with a domain associated with malicious activity.

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

1 flagged
3.1.4

Indicators of compromise (SHA-256)

d41cd8af4fc659204e641358eda189dac7d136a2918f8cec5c945431ced9a512
49bc14dd1e646ad9f2c8f14a5bac5de942fc43297f6d9fd3b7988ea0503b8f60
13afde2897e46ed6e7c2c2db7b4075ed3747bd3e791f24601816143eea1ad2d2
ab7da6a60f3957397adcc7d03869cb0ae892ccad91b47d0b535859f60b0d1fed
135351436969c90fa4cfd0e05a19d60a6e5b7c2531e9504549023d65812630d3

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove react-native-wm-barcode 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.

  3. Did it already run?

    If react-native-wm-barcode 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.

  4. How O3 protects you

    O3 blocks react-native-wm-barcode 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. react-native-wm-barcode on npm has been identified as a malicious package (version 3.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rjmw-8jgf-823rRLMA-2025-05137RLUA-2026-01530

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks react-native-wm-barcode-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.

Explore

react-native-wm-barcode (npm) malicious package — MAL-2025-45765 | O3 Security