Which versions of data-xabit are malicious?

Every published version of data-xabit on npm is considered malicious. Remove the package entirely.

How do I remediate data-xabit if I installed it?

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

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

Yes — data-xabit is associated with the GHSA-93wh-2c42-vrrj 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 data-xabit 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 data-xabit (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging data-xabit across your stack and pipelines.

Malicious package

data-xabitnpm

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

MAL-2025-191558

Immediate action

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

npm uninstall data-xabit

What this malware does

The package data-xabit 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

ef666e2a6f2f7477fb30dd787eaf97877e81e62aa9bbe396639b8c7beeebc5d3

03b37d6663928ececa76b6d1d4a4debb3e4e4cf163a4f8604f8e16d2df90548f

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

Campaign

GHSA-93wh-2c42-vrrj

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks data-xabit-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