levvleys
WhatsApp Web API Library
This report shows the evidence for levvleys@2.1.0. 26 of 29 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 23d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17397 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The automatic lifecycle hook is benign, but the embedded unreferenced multi-host buffer uploader is an unnecessary dormant capability with external disclosure potential. There is no completed malicious execution chain in this release.
Independent scan evidence
public snapshot- The package runs a preinstall hook automatically.
- An internal helper posts supplied buffers to third-party file-hosting services.
- The uploader has no in-package caller and is not exported, making it a dormant capability rather than a confirmed active attack.
- The preinstall script only checks the Node.js major version and exits if it is below 20.
- No self-dependency, credential harvesting, agent-control mutation, or import-time network request was found.
- The dynamic import is limited to loading the optional audio decoder for waveform generation.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603Findings
Affected versions and remediation
This report applies to levvleys@2.1.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing levvleys@2.1.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.