Which versions of create-remotion are malicious?

The following npm versions of create-remotion are flagged malicious: 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate create-remotion if I installed it?

create-remotion 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-remotion — how do I know if it already compromised me?

If create-remotion 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-remotion part of a known attack campaign?

Yes — create-remotion is associated with the GHSA-947j-5gjp-7968, IN-MAL-2026-011307, IN-MAL-2026-013209 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-remotion 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-remotion (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging create-remotion across your stack and pipelines.

Malicious package

create-remotionnpm

create-remotion is a confirmed malicious npm package (MAL-2026-11460) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in create-remotion (npm)

MAL-2026-11460

Immediate action

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

npm uninstall create-remotion

What this malware does

lib/report.js imports child_process, fs, https, and os and collects host identity and environment data via os.hostname(), os.userInfo(), execSync(...), and fs.readFileSync(...) calls at lines 20, 31, 72, 160 and 168. The collected data is sent via an https.request POST (lines 118, 121) to a hardcoded destination at hooks.zapier.com (line 12). The Zapier webhook is an author-controlled ingestion endpoint unrelated to any documented purpose of a create-remotion scaffolder, and the receiving of installer hostname, user info, and filesystem contents constitutes host reconnaissance and data exfiltration on install/run of the package.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

0.0.20.0.3

Indicators of compromise (SHA-256)

4f64eaf9a8b1571d5e5800922eededf88e925355ce9fa4d61c60d8b8c302401b

d31c0780d44a66914255959e786d3ef18ae49763037a2d714a0a610ef1cc1187

ed863be3e64bcb7233989a3fbaf6c410dbb13a0a437b02546f1f8fbe48511829

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-remotion (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging create-remotion across your stack and pipelines.
If you installed it — respond
create-remotion 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-remotion 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-remotion 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-remotion on npm has been identified as a malicious package (versions 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-947j-5gjp-7968IN-MAL-2026-011307IN-MAL-2026-013209

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks create-remotion-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