Which versions of react-video-canvas are malicious?

The following npm versions of react-video-canvas are flagged malicious: 9999.9999.10000. Treat any of these as compromised.

How do I remediate react-video-canvas if I installed it?

react-video-canvas 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 react-video-canvas — how do I know if it already compromised me?

If react-video-canvas 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 react-video-canvas part of a known attack campaign?

Yes — react-video-canvas is associated with the GHSA-pqv4-74gv-v429 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 react-video-canvas 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 react-video-canvas (version 9999.9999.10000). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-video-canvas across your stack and pipelines.

Malicious package

react-video-canvasnpm

Malicious code in react-video-canvas (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3189

Immediate action

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

npm uninstall react-video-canvas

What this malware does

Dependency confusion and typosquatting campaign by threat actor "saif777". Packages use inflated version numbers (9999.9999.9999, 9999.9999.10000, 50.50.50, 7.66.5) to win version resolution in environments with private registries. All active packages execute a postinstall hook ("node index.js") that collects a system fingerprint — public IP (via api.ipify.org), username, hostname, CPU model, RAM, working directory, OS platform — and exfiltrates it as a Discord embed to a shared webhook (base64-obfuscated in source). Payloads include sandbox/bot detection: machines with ≤1 CPU or <2 GB RAM are flagged as sandbox/CI; real machines trigger a green embed. Typosquats the react-video-canvas package.

The package react-video-canvas was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'react-video-canvas' @ 9999.9999.10000 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

9999.9999.10000

Indicators of compromise (SHA-256)

5b1137619aee1cf72b9f7fe20466eae167b78abf53ea92323b76e55055d1eb5f

ac8a8bf052602c43bc2579b2bc0a61b6ac8b2dbe83bc0272bd50deccf2031d3e

3cbd0cdc8dc308a9a6336734b65fea303841130cd953b64c43b024cc635444b1

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

Campaign

GHSA-pqv4-74gv-v429

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
SafeDep · finder

Detect & block this

O3 blocks react-video-canvas-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