Which versions of xpack-subscription are malicious?

The following npm versions of xpack-subscription are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate xpack-subscription if I installed it?

Remove xpack-subscription 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.

I already installed xpack-subscription — how do I know if it already compromised me?

If xpack-subscription 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.

Is xpack-subscription part of a known attack campaign?

Yes — xpack-subscription is associated with the GHSA-9f55-3p24-3r9c, RLMA-2026-01659, RLUA-2026-01837 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find xpack-subscription across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xpack-subscription (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xpack-subscription across your stack and pipelines.

Malicious package

xpack-subscriptionnpm

Malicious code in xpack-subscription (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1160

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall xpack-subscription

What this malware does

The package xpack-subscription was found to contain malicious code.

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.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

764e96f1c4197d6049674d2bbc6515f9d2de2682002cb53a8540f1f95f5c3694

62edc6bb089c839e93cf7b71b8b46ca1f5d064272cac586b49cda41fc40b1c19

d417dea6e9c46c73fa3e10620e00cbddf2b71d98ac11832df65605b3feddee52

60bcecb6430d0df36fc4252482d76327b760078265fceb4291091836e0cad733

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xpack-subscription (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xpack-subscription across your stack and pipelines.
If you installed it — respond
Remove xpack-subscription 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 xpack-subscription 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 xpack-subscription 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

No. xpack-subscription on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9f55-3p24-3r9cRLMA-2026-01659RLUA-2026-01837

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks xpack-subscription-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.

Malware detection Runtime egress monitoring