create-vercel-integration
This report shows the evidence for create-vercel-integration@1.0.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-5894 confirms this npm version as malicious.
Advisory
MAL-2026-5894
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in create-vercel-integration (npm)
Details
Package name mimics Vercel's official `create-*` initializer convention (e.g. `create-next-app`), targeting developers who mistype or guess the initializer name and invoke `npx create-vercel-integration`. The bin script (`bin/run.js`) hardcodes a callback URL `https://deepbounty.dd06-dev.fr/cb/f7506d76-f300-4c91-a105-41c07ad317fc` and, on invocation, reads the `INIT_CWD` environment variable, extracts its basename, and POSTs `{pkg, timestamp, transport, project}` to that author-controlled endpoint. The package self-describes as a 'Bug Bounty PoC,' but it is published on the public npm registry under a name shaped like an official Vercel scaffold and silently leaks the installer's project directory name to a third party with no disclosure or opt-out. The package provides no legitimate Vercel-integration scaffolding functionality; the bin's only effect is the beacon.
References
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 create-vercel-integration@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing create-vercel-integration@1.0.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: .
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.