Which versions of xpack-subscription-test are malicious?

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

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

Remove xpack-subscription-test 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-test — how do I know if it already compromised me?

If xpack-subscription-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is xpack-subscription-test part of a known attack campaign?

Yes — xpack-subscription-test is associated with the GHSA-cjg3-62x9-48px 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-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xpack-subscription-test (version 1.0.1).

Malicious package

xpack-subscription-testnpm

Advisory published Feb 4, 2026Updated Mar 3, 2026

xpack-subscription-test is a confirmed malicious npm package (MAL-2026-734) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xpack-subscription-test (npm)

MAL-2026-734

Immediate action

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

npm uninstall xpack-subscription-test

What this malware does

The package xpack-subscription-test 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.

The OpenSSF Package Analysis project identified 'xpack-subscription-test' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

b64529d3170b56ca6851ff656156935e22474ffb1254cf818ce555a976cda0a6

2447449c96d24d0c693d9105d432d9818fa96fb0c408fb371a3dc15167960feb

42b154d2787cdae3fd76744364ae77ae7ddb88ee0390fb00944630b2cbe8038b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for xpack-subscription-test (version 1.0.1).
If you installed it — respond
Remove xpack-subscription-test 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-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

GHSA-cjg3-62x9-48px

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database