autoreview

This fragment is highly suspicious due to numerous hardcoded secret/credential-like values (GitHub, Slack, AWS, and Bearer/JWT-like authorization) and calls to helper functions that likely resolve and/or read additional secrets. No explicit exfiltration or malicious sinks are visible in this snippet alone, but the credential exposure risk is extreme and the intent to use/manage authentication material is clear. Further review of the referenced helper implementations and downstream usage is necessary to confirm whether any exfiltration or malicious persistence occurs.

This code fragment contains clear supply-chain sabotage/test-harness behavior: during prompt rendering it writes a hostile MCP/Claude skill and a JS payload that runs execSync(`rm -rf uploads/${name}`), plus shell hook side effects. These are destructive/execution-capable mechanisms that go beyond safe secret scanning/redaction and would be extremely risky if triggered in real environments.