MAL-2026-14259 Malicious code in ranux-dev (npm)
Malicious package
Published
MAL-2026-14259 is a malicious package: ranux-dev (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-14259/ (Markdown: https://insights.sbomify.com/MAL-2026-14259/index.md)
- Package
- ranux-dev
- Registry
- npm
What is MAL-2026-14259?
MAL-2026-14259 is a malicious package in ranux-dev, published on 19 Aug 2026.
Official description
package.json declares the dependency
@whiskeysockets/baileys but resolves it from github:rcedubot/X instead of the npm registry. Installing ranux-dev pulls arbitrary, unpinned, mutable code from that personal GitHub account under the name of a widely-used WhatsApp Web library, and that code runs in the installer's Node process with full WhatsApp session and credential access. Every shipped source file (index.js, config.js, database.js, tenantManager.js, command.js, lib/.js, plugins/.js) is heavily obfuscated with obfuscator.io-style transforms and an RC4-over-base64 string decoder, so endpoints, credentials, and control flow cannot be reviewed statically. config.js exports a frozen SECRETS object with hardcoded encrypted strings alongside API_ENDPOINTS and NETWORK_CONFIG (MongoDB-shaped) constants. The combination — dependency substitution of a popular WhatsApp library from an unaffiliated GitHub account, uniform obfuscation across the tarball, a multi-tenant WhatsApp/MongoDB architecture, and shipped hardcoded credential-shaped constants — matches the session-harvester pattern in which installer WhatsApp sessions and tenant data are funneled to an author-controlled backend.What should I do about MAL-2026-14259?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.