@vinnxcode/xbailsyncnpm
Advisory published Updated
@vinnxcode/xbailsync is a confirmed malicious npm package (MAL-2026-11080) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @vinnxcode/xbailsync (npm)
What this malware does
@vinnxcode/xbailsync 1.0.1 is a fork/republish of the Baileys WhatsApp Web library. A a static rule fired on lib/Utils/generics.js due to co-occurrence of the tokens 'ping' and 'GET' in a utility file, which is the shape of network/HTTP helper code common to this library family. No concrete installer-harm path is present: there is no traced code that reads installer secrets (~/.aws, ~/.ssh, ~/.npmrc, env scraping, browser stores), no hardcoded attacker C2 destination bound to an exfiltration primitive, no install-time or import-time fetch-and-execute, no lifecycle scripts performing outbound network calls, and no dropper or backdoor mechanism. The pattern matched is keyword adjacency, not a demonstrable exfiltration flow.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @vinnxcode/xbailsync (2 malicious versions).
If you installed it — respond
@vinnxcode/xbailsync is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @vinnxcode/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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @vinnxcode/xbailsync-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.