ai-research-explore

No explicit malicious payload is present in this fragment, but it is a high-risk orchestration component: it ingests untrusted “command” strings from external campaign/variant files and forwards them to execution helper scripts via subprocess. It also modifies sys.path to load shared helper modules, which can enable supply-chain/path-hijack attacks if that directory is not strictly controlled. Overall, malware is unlikely to be proven from this file alone, but security risk is elevated due to delegated command execution and import-resolution changes.

This module is primarily a feasibility/resource planning tool with static parsing checks, but it also performs in-process dynamic execution of repository Python files during runtime “probe” checks (spec.loader.exec_module), with only stdout/stderr silenced and no sandboxing. No explicit credential theft/exfiltration/backdoor logic is visible in the fragment, so embedded malware is not demonstrated. However, the module’s design creates a meaningful supply-chain execution risk: if the target repository content or target_location_map can be influenced by an attacker, arbitrary code execution can occur within the scanning process. External GPU detection subprocesses and RESOURCE_PLAN.md output writing appear operationally intended and are lower risk than the dynamic exec behavior.