ecommerce-material-studio

No clear evidence of intentional malware (no network/exfiltration, subprocess execution, or credential theft). However, this module has meaningful security risks when plan/brand inputs and the runtime environment are not fully trusted: (1) dynamic import via sys.path mutation introduces a module-hijacking/code execution surface, (2) config/plan-controlled paths are used directly for Image.open (arbitrary local file reads of formats Pillow can open), (3) output filenames derived from img_id are not sanitized (possible path traversal/overwrite), and (4) unbounded image/text rendering can lead to denial-of-service. Treat this as a rendering utility that should be isolated, run with least privilege, and fed with trusted/sanitized plan and brand configuration.

This fragment is primarily a batch preprocessing/status-management orchestrator. It does not show direct malware behavior (no network activity, no eval/exec, no persistence, no classic exfiltration patterns). However, it has meaningful security risk from untrusted path handling: product['id'] is used directly as a directory component (enabling potential directory traversal/overwrites), CLI-provided --output-dir/--status-file are used without sandboxing, and status_file content can cause the tool to read and print arbitrary JSON from p['config_file']. It also executes local helper scripts with arguments derived from untrusted inputs, which increases the overall supply-chain/workflow attack surface even though this module itself avoids shell=True.