0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
lekzo-baileys
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting lekzo-baileys, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-16276 | Unknown | Malicious code in @lekzo/baileys (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (da5caafea4a5656343feb4b52bf0007c98e6ed65a41ad22c79f24c0f1c48566f) package.json declares the `libsignal` dependency as `github:canove/libsignal-node` — a bare GitHub owner/repo reference with no commit SHA, tag, or semver version. On `npm install`, this resolves to whatever the current HEAD of that third-party repository points at, fetching and installing arbitrary code with no integrity check and running any lifecycle scripts inside the returned bytes. Whoever controls that GitHub repository at any future |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (da5caafea4a5656343feb4b52bf0007c98e6ed65a41ad22c79f24c0f1c48566f) package.json declares the `libsignal` dependency as `github:canove/libsignal-node` — a bare GitHub owner/repo reference with no commit SHA, tag, or semver version. On `npm install`, this resolves to whatever the current HEAD of that third-party repository points at, fetching and installing arbitrary code with no integrity check and running any lifecycle scripts inside the returned bytes. Whoever controls that GitHub repository at any future