xo-member-componentsnpm
xo-member-components is a confirmed malicious npm package (MAL-2026-11063) that executes malicious code on install (malicious versions 8.0.0, 28.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in xo-member-components (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xo-member-components (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xo-member-components across your stack and pipelines.
If you installed it — respond
Remove xo-member-components from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If xo-member-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 xo-member-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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks xo-member-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.