drupal-contrib-mgmt
Fail
Audited by Gen Agent Trust Hub on Feb 16, 2026
Risk Level: HIGHEXTERNAL_DOWNLOADSREMOTE_CODE_EXECUTIONCOMMAND_EXECUTION
Full Analysis
- [EXTERNAL_DOWNLOADS] (HIGH): The scripts 'find-and-apply-patch.sh', 'major-version-upgrade.sh', and 'update-with-patch.sh' download .patch files from drupal.org. Although this is a standard community source, it is not within the whitelisted trusted sources, and unauthenticated downloads of executable patches are inherently risky.
- [REMOTE_CODE_EXECUTION] (HIGH): Multiple scripts automate the application of these remote patches to the local filesystem using the 'patch' utility or 'composer'. This allows for arbitrary code modification and execution on the host system without any prior verification of the patch content's integrity.
- [COMMAND_EXECUTION] (MEDIUM): The scripts make heavy use of shell commands like 'composer', 'drush', and 'git' to modify system configuration files (composer.json). While the input for these commands is currently hardcoded, the pattern of appending unvalidated strings to configuration files is a potential vector for system instability or security bypass.
- [INDIRECT_PROMPT_INJECTION] (HIGH): Mandatory Evidence Chain: 1. Ingestion points: Remote patch URLs in 'find-and-apply-patch.sh', 'major-version-upgrade.sh', and 'update-with-patch.sh'. 2. Boundary markers: None present; the scripts treat the remote content as trusted code. 3. Capability inventory: 'patch -p1' and 'composer install' provide direct code execution and modification capabilities. 4. Sanitization: None. The scripts do not perform any checksum validation or signature verification of the downloaded patches before they are applied to the codebase.
Recommendations
- AI detected serious security threats
Audit Metadata