Which versions of @vinnxcode/xbailsync are malicious?

The following npm versions of @vinnxcode/xbailsync are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @vinnxcode/xbailsync if I installed it?

@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.

I already installed @vinnxcode/xbailsync — how do I know if it already compromised me?

If @vinnxcode/xbailsync 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 @vinnxcode/xbailsync part of a known attack campaign?

Yes — @vinnxcode/xbailsync is associated with the GHSA-fgwc-g3q5-794p, IN-MAL-2026-013129, IN-MAL-2026-013127 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 @vinnxcode/xbailsync 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 @vinnxcode/xbailsync (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vinnxcode/xbailsync across your stack and pipelines.

Malicious package

@vinnxcode/xbailsyncnpm

@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)

MAL-2026-11080

Immediate action

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

npm uninstall @vinnxcode/xbailsync

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

9107de0deb8cfa91ef2bb3ca6de2af14aa715a3bb70fb110146a62e3185a1c94

587f6ecfc8db23da5b8638d57f79df61081d6d177ae2233ce12e6e7f3a6ac8ab

aa85bc699ec69bbebf0799696e784cee3fcd9f78f5ccc9e2cb032e9a9cb3de68

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @vinnxcode/xbailsync (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vinnxcode/xbailsync across your stack and pipelines.
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 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 @vinnxcode/xbailsync 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. @vinnxcode/xbailsync 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-fgwc-g3q5-794pIN-MAL-2026-013129IN-MAL-2026-013127

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database