Which versions of create-vercel-integration are malicious?

The following npm versions of create-vercel-integration are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate create-vercel-integration if I installed it?

create-vercel-integration is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed create-vercel-integration — how do I know if it already compromised me?

If create-vercel-integration was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is create-vercel-integration part of a known attack campaign?

Yes — create-vercel-integration is associated with the IN-MAL-2026-006757 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find create-vercel-integration across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for create-vercel-integration (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging create-vercel-integration across your stack and pipelines.

Malicious package

create-vercel-integrationnpm

create-vercel-integration is a confirmed malicious npm package (MAL-2026-5894) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in create-vercel-integration (npm)

MAL-2026-5894

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall create-vercel-integration

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

aeaea6bab6360c38ed5a7de7065eb04d0ac489bb3670b68defc8bc26874d3d62

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for create-vercel-integration (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging create-vercel-integration across your stack and pipelines.
If you installed it — respond
create-vercel-integration is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If create-vercel-integration was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks create-vercel-integration before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. create-vercel-integration on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006757

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks create-vercel-integration-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database