video
Audited by Socket on Jul 2, 2026
3 alerts found:
Anomalyx2SecurityNo explicit malicious behavior (e.g., network exfiltration, credential theft, obfuscation, eval/Function usage, or system-destruction commands) is present in the provided fragment. However, the code heavily relies on executing other scripts/tools (node tts.mjs, ensure-remotion.mjs, and pnpm/Remotion) using untrusted inputs derived from user-provided JSON files and, notably, passes the entire process.env into the TTS subprocess. This creates meaningful supply-chain/execution risk typical of render pipelines: if any downstream script or dependency is compromised, the pipeline will execute it with access to environment variables and attacker-controlled props.
This module does not show direct indicators of covert malware (no obfuscated payloads, backdoors, or explicit data theft/exfiltration). However, it materially increases supply-chain risk impact by (1) copying optional .npmrc into a persistent shared directory, (2) running pnpm install there (which can execute dependency lifecycle/build scripts), and (3) symlinking the resulting shared node_modules into the project so later executions run from that shared tree. The script is likely a legitimate bootstrapper, but it is inherently high-impact and should be used only with trusted package inputs and a trusted shared directory.