Vulnerability Database · npm · @zeronexcode/baileys · Version

@zeronexcode/baileys 0.0.0-stage

0.0.0-stage is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

Released 12 Oct 2026 Also known from other sources 1 Newer releases 2 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

@zeronexcode/baileys 0.0.0-stage vulnerabilities

1 vulnerability cover @zeronexcode/baileys 0.0.0-stage. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Malicious Auto-Following Behavior in @zeronexcode/baileys Package N/A critical No fix published 25 Sep 2026

Looking for another version, or everything Vulert holds for @zeronexcode/baileys?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @zeronexcode/baileys 0.0.0-stage

Is @zeronexcode/baileys 0.0.0-stage vulnerable?

Yes. 1 vulnerability in the Vulert database cover @zeronexcode/baileys 0.0.0-stage: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 0.0.0-stage the latest release of @zeronexcode/baileys?

No. 0.0.0-stage was published 12 Oct 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor @zeronexcode/baileys for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @zeronexcode/baileys version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.