# MAL-2026-12424: Malicious code in react-native-ui-message (npm)


- **Type:** Malicious package
- **Package:** `react-native-ui-message` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-w3j6-3pww-qfcw

## What is MAL-2026-12424?

MAL-2026-12424 is a malicious package in react-native-ui-message, published on 5 Aug 2026. 

### Official description

react-native-ui-message@1.0.0 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.

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.

## What should I do about MAL-2026-12424?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12424 is a malicious package: react-native-ui-message (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12424/ (Markdown: https://insights.sbomify.com/MAL-2026-12424/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12424

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12424/
Summaries are generated and may contain mistakes; the official description above is the record.