MAL-2026-17155 Malicious code in @osl-design/react (npm)
Malicious package
Published
MAL-2026-17155 is a malicious package: @osl-design/react (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-17155/ (Markdown: https://insights.sbomify.com/MAL-2026-17155/index.md)
- Package
- @osl-design/react
- Registry
- npm
What is MAL-2026-17155?
MAL-2026-17155 is a malicious package in @osl-design/react, published on 24 Sep 2026.
Official description
The package declares
"install": "node index.js" in package.json, so npm install automatically executes its top-level script. That script loads runtime/support/telemetry/probe/impl.js, which reads the installer's OS username (os.userInfo().username), hostname (os.hostname()), and current working-directory basename, concatenates them with a prefix into a DNS label, and issues a dns.resolve4 query against the hardcoded domain oob.algamil7x.xyz — a DNS out-of-band exfiltration channel. Sensitive strings, including the module names os/dns, the API names userInfo/hostname/cwd/resolve4, the label prefix osldr, and the destination domain oob.algamil7x.xyz, are hidden as hex/char-code arrays decoded at runtime, and os and dns are loaded through module.constructor._load(...) rather than literal require() calls to evade static analysis. The README contradicts the shipped behavior by asserting the package has no file system access and no network requests beyond registry probes, and the scope name @osl-design/react resembles a design-system package to lend plausibility. Installing this package leaks host-identifying information about the installer's machine to an attacker-controlled DNS resolver.What should I do about MAL-2026-17155?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.