MAL-2026-5522 Malicious code in @orion-design-system/components (npm)
Malicious package
Published
MAL-2026-5522 is a malicious package: @orion-design-system/components (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-5522/ (Markdown: https://insights.sbomify.com/MAL-2026-5522/index.md)
- Package
- @orion-design-system/components
- Registry
- npm
What is MAL-2026-5522?
MAL-2026-5522 is a malicious package in @orion-design-system/components, published on 10 Jun 2026.
Official description
package.json declares a
preinstall hook that runs an inline node -e script reading os.hostname() and os.userInfo().username and transmitting them via HTTPS GET (and a DNS lookup) to d8kn5vlt5p5h1j34mbcgbx1nffwjobfoh.oast.fun, an interactsh/OAST callback subdomain not controlled by the installer. The hook fires automatically on npm install, with no opt-out. The package is published under the @orion-design-system scope at version 9999.0.0 — the canonical dependency-confusion bait version — and the README names Cloud Imperium Games / Roberts Space Industries as the intended target, confirming the package is positioned to be resolved over a private internal package of the same name. Any installer whose resolver picks the public version (intentionally or via misconfiguration) leaks host identifiers to a third-party collection endpoint on install. The 9999.0.0 version pin combined with the scope-targeted README and unconditional install-time beacon places this firmly in the active-attack / dependency-confusion-exfil pattern, regardless of any research framing.What should I do about MAL-2026-5522?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.