Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

xbailsyncnpm

Advisory published Updated

xbailsync is a confirmed malicious npm package (MAL-2026-16093) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xbailsync (npm)

MAL-2026-16093
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall xbailsync

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

9 flagged
1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.72.0.0

Indicators of compromise (SHA-256)

37b2c945ecd2da7d2c6d4987cf7101250483335439ac0d5f2ac94937643cd61a
18ff4aa1a565659c7106700fc5b7c355770ec8fc6bd62c0d9a4f8efce56bf09f
2143ab8d5ba5d421c48e0c8f8f93976ed2e259b160b1f54dedf92fd036280972
409b29e9e44b499e3c7441f5269555e26a4b7baadc0f310ea585f9241d648901
4aa3d3f047949d2e8edd9e477a312ed7c2e92b3a09d8d94a18145d609da29c29
baab2774609811e288fdba66a33dc1421acbf708dbc2dfd88be604a409167c43
c8daaabd3b8451edf2203329e5ce2b4b3d7031aaf9ac14986a281915e6e35e8a
17ce5200f29898697e35ba5381ac8f7f4fcc3f71e0b3f0eda657281ff1b3186f
74f56fa9d21bad36867fa01698d072d94d620045f3af5f4490eb3993ed1ea7b3
7dfff38d75060e38f2419c28c6dfffa9f9b19abedbb5499668d2a4c7bea394de

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for xbailsync (9 malicious versions).

  2. If you installed it — respond

    Remove xbailsync 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.

  3. Did it already run?

    If xbailsync 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. xbailsync on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vfrg-29g4-854pIN-MAL-2026-019890IN-MAL-2026-019891IN-MAL-2026-019884IN-MAL-2026-019886IN-MAL-2026-019892IN-MAL-2026-019885IN-MAL-2026-019887IN-MAL-2026-019888IN-MAL-2026-019889

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks xbailsync-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.

Explore

xbailsync (npm) malicious package — MAL-2026-16093 | O3 Security