implicit-cad
Audited by Socket on Aug 21, 2026
3 alerts found:
Anomalyx2SecurityThis module is a CAD generation orchestrator that dynamically loads and executes Python generator plugins from a filesystem path (exec_module + generator() call). It validates the *returned payload structure* but cannot restrict what the plugin code does during import/execution. No explicit overt malware (network exfiltration, credential theft, reverse shell) is visible in this fragment; the primary risk is the inherent arbitrary-code-execution trust boundary, which would enable build-time sabotage or data theft if an attacker can influence the generator module path/content. Truncation at the end of the file slightly limits review of cleanup/lock semantics.
This code is not overtly malicious in isolation (no explicit credential theft or exfiltration logic present), but it provides high-impact arbitrary JavaScript execution primitives via dynamic `import()` from caller-controlled URLs and by importing caller-controlled source encoded as a `data:text/javascript` module. If untrusted `url` or `source` can reach these functions, the security risk is substantial; the safest use requires strict allowlisting/validation and/or sandboxing at the call site.
This module is a minimal bootstrap that registers a local Node.js resolution hook (node_resolve_hooks.mjs) using the privileged node:module register mechanism. While the snippet itself shows no explicit malicious actions, the hook-based approach is high-impact and can be used to alter dependency resolution/execution, making it a supply-chain/runtime tampering red flag pending review and verification of node_resolve_hooks.mjs (content, integrity, and whether it only performs intended legitimate resolution behavior).