# MAL-2026-11063: Malicious code in xo-member-components (npm)


- **Type:** Malicious package
- **Package:** `xo-member-components` (npm)
- **Published:** 25 Jul 2026
- **Also known as:** GHSA-r5v8-7g3c-jp8w

## What is MAL-2026-11063?

MAL-2026-11063 is a malicious package in xo-member-components, published on 25 Jul 2026. 

### Official description

index.js runs as a preinstall lifecycle script on npm install. It collects host identity and network configuration — os.hostname(), os.platform(), os.arch(), os.homedir(), and dns.getServers() — serializes the values as JSON, and POSTs them via https.request to the hardcoded host bq5y8jbk0j29x3az0p1p931i69c10sqgf.oastify.com at path /hit. oastify.com is the Burp Collaborator out-of-band callback service; the unique subdomain identifies a specific operator's collector. Installing the package causes the installer's host identifiers to leave the machine to an attacker-controlled destination. The package presents itself as a dependency-confusion proof of concept, which does not change the installer-side effect.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'xo-member-components' @ 28.0.0 (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-11063?

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-11063 is a malicious package: xo-member-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-11063/ (Markdown: https://insights.sbomify.com/MAL-2026-11063/index.md)
```

## Sources

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

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