Which versions of xdater are malicious?

The following npm versions of xdater are flagged malicious: 6.1.9, 6.2.0. Treat any of these as compromised.

How do I remediate xdater if I installed it?

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

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

Yes — xdater is associated with the GHSA-66hc-2r75-vwxf, RLMA-2025-06003, RLUA-2025-06542 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 xdater 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 xdater (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xdater across your stack and pipelines.

Malicious package

xdaternpm

xdater is a confirmed malicious npm package (MAL-2025-48951) that executes malicious code on install (malicious versions 6.1.9, 6.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xdater (npm)

MAL-2025-48951

Immediate action

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

npm uninstall xdater

What this malware does

The package xdater 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

6.1.96.2.0

Indicators of compromise (SHA-256)

352b4b106eecd6bc552fbe402da0fc80f976f9c06608453792e9b1c33a1836ff

b641058c31a73a57e1f88b0d8530757deb8d58bb5cab44d8d6804838e51ad66e

67bc68a4b569d10a1de7b7e65bac20db769daa9bd3629c83c07d39e1b07ccd3d

9bca05a2805ea19ac75e4b7cf8e4c6927a62c8c7b712a500cf73534731598e49

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

Campaign

GHSA-66hc-2r75-vwxfRLMA-2025-06003RLUA-2025-06542

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks xdater-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