distributed-mesh

SUSPICIOUS: The skill’s purpose and capabilities are mostly aligned, and it does not obviously harvest credentials or route data through attacker-controlled gateways. Risk comes from executing opaque bundled scripts and from syncing untrusted remote content that agents may later treat as local trusted context.

No explicit malware/backdoor is evident in the snippet, but the code is security-sensitive: it performs arbitrary git and HTTP fetching based on mesh.json, writes fetched content into configuration-controlled local paths, and uses eval to execute a constructed curl command. Additionally, when bearer auth is enabled, it reads a secret from an environment variable and sends it as an Authorization header to a URL chosen by mesh.json. If mesh.json (or the relevant environment token) is attacker-influenced, this creates substantial supply-chain compromise and command-injection/secret-exposure risk. Recommend eliminating eval, validating/allowlisting URLs and destination paths, and constraining operations to a fixed workspace.