tenderly
Audited by Socket on Aug 4, 2026
1 alert found:
AnomalyNo overt supply-chain malware indicators are present in this fragment (no obfuscation, dynamic execution, filesystem/process access, or credential harvesting). The main risk is security design: the webhook-triggered action uses an operator private key to execute privileged `pause()`/`unpause()` transactions on a contract address supplied by an untrusted webhook payload, with only minimal validation and no shown authentication/authorization or contract allowlist enforcement. This makes the module potentially dangerous if the webhook endpoint is reachable or insufficiently protected; the Slack/RPC egress paths are consistent with intended monitoring/reporting but would also amplify impact if secrets are compromised.