Which versions of xpack-per-device are malicious?

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

How do I remediate xpack-per-device if I installed it?

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

If xpack-per-device 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-per-device part of a known attack campaign?

Yes — xpack-per-device is associated with the GHSA-9629-h7qc-p57c, RLMA-2026-01658, RLUA-2026-01836 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-per-device 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-per-device (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-per-device across your stack and pipelines.

Malicious package

xpack-per-devicenpm

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

MAL-2026-1159

Immediate action

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

npm uninstall xpack-per-device

What this malware does

The package xpack-per-device 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)

40c08125e60c3d43432e40679e35d49bb3fc0b9d4a3df799c45b80999f1753d0

5f3e144fc188f6f28820784883e158f5841d1276a3eb100db4c469e45439f415

d523ac9846cc69ac826c7a989516cf491be17b08e5ca45b85e3fc1108d0f26d8

15edf1e1ecddce3f234beb3ebf306c582e3bea2a4bf76a1311faeed42b96c3c6

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-per-device (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-per-device across your stack and pipelines.
If you installed it — respond
Remove xpack-per-device 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-per-device 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-per-device 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-per-device 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-9629-h7qc-p57cRLMA-2026-01658RLUA-2026-01836

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks xpack-per-device-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