# MAL-2026-5523: Malicious code in @orion-design-system/foundation (npm)


- **Type:** Malicious package
- **Package:** `@orion-design-system/foundation` (npm)
- **Published:** 10 Jun 2026

## What is MAL-2026-5523?

MAL-2026-5523 is a malicious package in @orion-design-system/foundation, published on 10 Jun 2026. 

### Official description

The package's npm preinstall lifecycle script runs an inline `node -e` payload that collects the installer's hostname (`os.hostname()`) and OS username (`os.userInfo().username`) and transmits both to an attacker-controlled ProjectDiscovery Interactsh listener at `d8ks495t5p5ut2enft80hii4hqu7wt7gb.oast.site` — first as an HTTPS GET with the values in query parameters (`?h=<hostname>&u=<username>`), then as a DNS lookup encoding the hostname into a subdomain (dual-channel to bypass egress filtering). The attacker controls the unique OAST subdomain and receives both the HTTP request and the DNS query out-of-band. The version `9999.0.4` and the `@orion-design-system` scope are the canonical fingerprints of a dependency-confusion attack: a high version number is published to public npm under a scope that the attacker believes corresponds to a private/internal package, so any victim build that misroutes resolution to the public registry will pull this version and execute the exfiltration on `npm install`.

The OpenSSF Package Analysis project identified '@orion-design-system/foundation' @ 9999.0.4 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

## What should I do about MAL-2026-5523?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5523 is a malicious package: @orion-design-system/foundation (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-5523/ (Markdown: https://insights.sbomify.com/MAL-2026-5523/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5523

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5523/
Summaries are generated and may contain mistakes; the official description above is the record.