MAL-2026-5425 Malicious code in @oplus/obus-web-sdk (npm)
Malicious package
Published
MAL-2026-5425 is a malicious package: @oplus/obus-web-sdk (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-5425/ (Markdown: https://insights.sbomify.com/MAL-2026-5425/index.md)
- Package
- @oplus/obus-web-sdk
- Registry
- npm
What is MAL-2026-5425?
MAL-2026-5425 is a malicious package in @oplus/obus-web-sdk, published on 9 Jun 2026.
Official description
On
npm install, the package's scripts/postinstall.js collects the installer's username (os.userInfo()), hostname (os.hostname()), current working directory (process.cwd()), and public IP (fetched from https://api.ipify.org), then exfiltrates the data to a hardcoded interactsh C2 subdomain xjaipnfhcpawuhzlgzkzo1ak3aai9m873.oast.fun through two channels: a DNS lookup with the hex-encoded payload as a subdomain, and an HTTPS GET to /poc carrying the data base64-encoded in an x-poc header. The package uses the @oplus scope (impersonating OPlus/Oppo internal namespaces) and is published at version 99.99.99 — the canonical dependency-confusion pattern designed to outrank any legitimate internal release during resolution. The in-source comment framing this as a benign PoC does not change the installer-side harm: any build that resolves @oplus/obus-web-sdk against the public registry will leak host/user/IP/cwd to attacker infrastructure.What should I do about MAL-2026-5425?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.