react-native-ui-messagenpm
react-native-ui-message is a confirmed malicious npm package (MAL-2026-12424) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in react-native-ui-message (npm)
What this malware does
[email protected] declares a postinstall hook that runs src/utilities/SubscriptionGuard.js. On install the script enumerates non-internal network interfaces via os.networkInterfaces() to obtain the host's MAC address, then POSTs {mac, os: process.platform, path: __dirname} to https://react-native-ui-message.com/api/EntitlementState. It then issues a GET to https://react-native-ui-message.com/api/ValidateLicense/... and passes the response body to Node's vm.runInContext with a context exposing require/process/Buffer, executing arbitrary server-returned JavaScript on the installer's machine. The accompanying integrity check compares a constant string against itself, so no verification of the fetched code occurs. The package presents itself as a pure-JS React Native toast/message component, for which no license-server-controlled remote code path is required.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-native-ui-message (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-native-ui-message across your stack and pipelines.
If you installed it — respond
Remove react-native-ui-message 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 react-native-ui-message 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 react-native-ui-message 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks react-native-ui-message-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.