@vapi-ai/server-sdk
This report shows the evidence for @vapi-ai/server-sdk@1.2.2. 4 of 6 known versions are blocked or flagged. The newest version, 3.0.0, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-5209 confirms this npm version as malicious.
Advisory
MAL-2026-5209
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @vapi-ai/server-sdk (npm)
Details
The package was found to contain malicious code or consuming dependency that contains malicious code
## Source: google-open-source-security (a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb) The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized `binding.gyp` files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @vapi-ai/server-sdk@1.2.2.
The same advisory and Firewall decision cover 4 recorded versions
0.11.1, 0.11.2, 1.2.1, 1.2.2
The versions list below shows the verdict for each recorded version.
- Avoid installing @vapi-ai/server-sdk@1.2.2. 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: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.