Which versions of npm-xmt are malicious?

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

How do I remediate npm-xmt if I installed it?

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

If npm-xmt 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 npm-xmt part of a known attack campaign?

Yes — npm-xmt is associated with the GHSA-2fqg-43mh-6h87, RLMA-2026-01466 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 npm-xmt 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 npm-xmt (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-xmt across your stack and pipelines.

Malicious package

npm-xmtnpm

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

MAL-2025-192987

Immediate action

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

npm uninstall npm-xmt

What this malware does

The package npm-xmt 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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

66603f4e5606fa61cf79355902ed86e376156cd0b163be93e0b471b87180e0b2

fcf1d57a75f915c7959a484b36e4b23c72425b90256a860d8d52e058599af296

d69c9a6f591510c352d6fc694437c62acf414b69eee5a9d26d7d868f311a859e

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 npm-xmt (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-xmt across your stack and pipelines.
If you installed it — respond
Remove npm-xmt 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 npm-xmt 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 npm-xmt 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. npm-xmt on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2fqg-43mh-6h87RLMA-2026-01466

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks npm-xmt-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