- Home
- Skills
- APIs & Backend
- Webhook Handler Safety Check
More screenshots
Works with the AI Agents you already use
Webhook Handler Safety Check
A route that reads X-Shopify-Topic and ships the order, but never checks X-Shopify-Hmac-Sha256, ships orders for anyone who finds the URL.
$5
Webhook Handler Safety Check
Example session with this skill installed
Check this project with webhook-handler-safety-check.
- Read your context and instructions
- Compiled the webhook handler safety
$ python3 scripts/check_webhooks.py examples/risky
BLOCK app/Http/Middleware/VerifyPaddleSignature.php:13 W03 VERIFICATION_DISABLED
if (! $secret) {
Why: Signature verification is switched off or fails open: twilio.webhook({ validate: false }), @octokit/webhooks receive() (it runs the handlers without checking the signature), or a check that returns true or calls next() when the signature header or the secret is missing. An attacker just leaves the header out.
Safer: Answer 401 or 403 when the signature or the secret is missing, use verifyAndReceive() instead of receive(), and keep validate on (sign test payloads with a test secret instead).
BLOCK routes/shopify.js:5 W01 NO_SIGNATURE_VERIFICATION
BLOCK routes/sms.js:7 W03 VERIFICATION_DISABLED
BLOCK server.js:8 W02 WEBHOOK_SECRET_IN_CODE
REVIEW hooks/clerk.py:16 W13 NO_TIMESTAMP_CHECK
REVIEW routes/shopify.js:7 W14 NO_EVENT_DEDUP
REVIEW routes/sms.js:12 W17 VERIFICATION_CAN_BE_SKIPPED
REVIEW server.js:9 W16 SECRET_FALLBACK_VALUE
REVIEW server.js:12 W15 LEGACY_SHA1_SIGNATURE
REVIEW server.js:13 W15 LEGACY_SHA1_SIGNATURE
REVIEW server.js:14 W12 HMAC_OVER_PARSED_BODY
REVIEW server.js:15 W11 SIGNATURE_COMPARED_WITH_EQUALS
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 5 with webhook handler content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A route that reads X-Shopify-Topic and ships the order, but never checks X-Shopify-Hmac-Sha256, ships orders for anyone who finds the URL. So does an HMAC computed over JSON.stringify(req.body), a twilio.webhook({ validate: false }) left over from testing, or a check that returns true when the signature header is missing. This skill finds those and seven other webhook mistakes before the endpoint goes live, and tells you how to fix each one.
Your agent runs a scanner on your webhook code in JavaScript and TypeScript (Express, Next.js, NestJS, Hono, Koa, Fastify), Python (Flask, FastAPI, Django, AWS Lambda), PHP (Laravel), Ruby (Rails, Sinatra) and Go. It finds each route and treats a POST route as a GitHub, GitLab, Shopify, Twilio, Paddle, Lemon Squeezy, Polar, Svix, Clerk, Resend, SendGrid, Mailgun, Square, Razorpay or Coinbase receiver when it reads that provider's headers or event payload. It checks each route on its own and knows each provider's verification calls (octokit verify, authenticate.webhook, twilio.webhook(), paddle.webhooks.unmarshal, validateEvent, verifyWebhook, Svix Webhook.verify and more), so verified routes, and routes covered by a verifying middleware, decorator or helper in another scanned file (Express app.use, Go handler wrappers, Next.js middleware, Rails before_action and Rack::TwilioWebhookAuthentication), are not reported. It skips comments and test files and never runs your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- W01: POST routes that read a provider's webhook headers or payload with no signature verification
- W02: webhook signing secrets, provider keys and GitLab tokens written in the code
- W03: verification switched off or failing open (validate: false, octokit receive(), letting the request through when the signature or secret is missing, rejecting only when a signature is present, or going on after a failed verify)
REVIEW
- W11: signatures compared with ==, ===, strcmp or bytes.Equal instead of a constant-time comparison
- W12: HMACs computed over re-serialized JSON instead of the raw request body
- W13: hand-written checks of timestamped signatures with no time window (replay)
- W14: order and payment events handled with no event-id or duplicate check
- W15: GitHub's legacy SHA-1 X-Hub-Signature or Square's legacy signature header
- W16: webhook secrets read from the environment with a hard-coded fallback value
- W17: verification that an environment setting or a SKIP_ or DISABLE_ flag can turn off
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and provider documentation link for each rule
- A risky and a safe example project, and the real report the scanner produces on the risky one
Limits It reads code as written: verification done by an API gateway, a proxy or code outside the scanned folder is not seen, and values built across several files are not followed. A route that only names a provider in its path is not treated as a webhook receiver. Stripe webhooks are not covered. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Static check of webhook handler source text. Provider dashboard settings and verification done outside the scanned code are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert secrets (notreal-..., ...EXAMPLE) for the scanner to find. It is never run.