@orion-design-system/componentsnpm
Malicious code in @orion-design-system/components (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @orion-design-system/components (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @orion-design-system/components across your stack and pipelines.
If you installed it — respond
@orion-design-system/components establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @orion-design-system/components was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @orion-design-system/components before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @orion-design-system/components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.