openscad
Audited by Socket on Sep 13, 2026
4 alerts found:
Securityx2Anomalyx2The code is a legitimate-looking OpenSCAD validation utility, but it contains a high-severity arbitrary JavaScript execution risk because eval() processes values derived from the input file. It also has a command-injection risk from interpolating an untrusted file path into execSync shell commands. These are security vulnerabilities and should be fixed by parsing literals without eval and by using execFileSync/spawn with an argument array. No clear malware behavior such as data theft, persistence, or network exfiltration is present in the shown fragment.
The code appears to be a legitimate OpenSCAD geometry analysis CLI and shows no indicators of intentional malware. However, it contains a medium-severity command-injection risk because the user-controlled filePath is inserted into a shell command executed by execSync. Use spawn/spawnSync with an argument array or properly avoid shell interpretation, and add validation and size limits for STL parsing. Malformed input can also cause denial-of-service conditions through unchecked binary STL triangle counts.
The code is a legitimate-looking OpenSCAD test runner and contains no clear malware indicators or data-exfiltration behavior. It has two important code-execution risks: unsafe shell command construction in runWithParams() and eval() of SCAD-derived expressions. It should use spawnSync/execFile with an argument array, validate parameter names and values, and replace eval with a restricted numeric-expression parser. The fragment is syntactically invalid as displayed because of a malformed string literal.
The code does not show evidence of malware, data theft, persistence, cryptomining, or backdoor behavior. It has a security-relevant command-injection vulnerability because the user-controlled SCAD filename is interpolated into a shell command without robust escaping. Use execFileSync() with an argument array, validate the path, and perform temporary-file cleanup in a finally block. Confidence is high because the vulnerable data flow is explicit.