--- name: webhook-security-0fcfba30ddba description: >- Verifies webhook signatures, blocks replayed requests and deduplicates retries on a webhook receiver. Use when a user asks to verify webhook signatures, prevent replay attacks, handle webhook retries, or build a secure webhook endpoint for Stripe, GitHub, Slack, or any HMAC-signing provider. license: Apache-2.0 compatibility: 'Any language/framework' metadata: author: terminal-skills version: 1.1.0 category: devops repository: https://github.com/stripe/stripe-node tags: "webhooks, security, signatures, hmac, api" --- # Webhook Security ## Overview Webhooks deliver real-time data to your app, but an open endpoint is an attack surface. Without verification, anyone can POST fake events to your webhook URL. This skill covers signature verification, replay protection, idempotency, and reliable processing patterns. ## Instructions ### Step 1: Signature Verification Every major provider signs webhook payloads with HMAC. Verify before processing. ```typescript // lib/webhooks/verify.ts — Generic HMAC verification import crypto from 'crypto' export function safeEqual(a: string, b: string): boolean { const x = Buffer.from(a) const y = Buffer.from(b) // timingSafeEqual THROWS (ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH) when lengths differ return x.length === y.length && crypto.timingSafeEqual(x, y) } export function verifyHmacSignature( payload: string | Buffer, signature: string, secret: string, algorithm: string = 'sha256' ): boolean { const expected = crypto .createHmac(algorithm, secret) .update(payload) .digest('hex') return safeEqual(signature, expected) } ``` Providers differ in header name, prefix (`sha256=`), encoding (hex or base64) and what is signed (body only, or timestamp + body). Read the provider's docs for each, and keep the secret in an environment variable. ### Step 2: Stripe Webhook Verification ```typescript // routes/webhooks/stripe.ts — Stripe webhook handler import Stripe from 'stripe' const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!) // current stripe-node: 23.x export async function handleStripeWebhook(req: Request) { const body = await req.text() // raw body, NOT parsed JSON const sig = req.headers.get('stripe-signature')! let event: Stripe.Event try { event = stripe.webhooks.constructEvent( body, sig, process.env.STRIPE_WEBHOOK_SECRET! ) } catch (err) { console.error('Webhook signature verification failed:', (err as Error).message) return new Response('Invalid signature', { status: 400 }) } // Process event idempotently (see Step 3) switch (event.type) { case 'checkout.session.completed': await handleCheckoutComplete(event.data.object) break case 'invoice.payment_failed': await handlePaymentFailed(event.data.object) break case 'customer.subscription.deleted': await handleSubscriptionCanceled(event.data.object) break } return new Response('OK', { status: 200 }) } ``` `constructEvent` checks the `t=` timestamp in the header against a 5-minute tolerance by default. Never pass a tolerance of `0`: that disables the recency check. On runtimes without Node's `crypto` sync API (Cloudflare Workers, Deno, browsers) use `await stripe.webhooks.constructEventAsync(body, sig, secret)`. Each Stripe endpoint has its own `whsec_` secret; the Stripe CLI prints a different one for `stripe listen`. ### Step 3: Replay Protection and Idempotency ```typescript // lib/webhooks/idempotency.ts — Prevent duplicate processing import { redis } from '../redis' export async function processOnce( eventId: string, handler: () => Promise ): Promise { // Set with NX (only if not exists) and a 3-day expiry (Stripe retries for up to 3 days) const isNew = await redis.set(`webhook:${eventId}`, '1', 'NX', 'EX', 259200) if (!isNew) { console.log(`Duplicate webhook ${eventId}, skipping`) return false } try { await handler() return true } catch (err) { // Remove key so retry can work await redis.del(`webhook:${eventId}`) throw err } } // Usage: Stripe retries for up to three days, so the key must outlive a retry // window you care about. Better still, make the handler itself idempotent. await processOnce(event.id, async () => { await db.order.update({ where: { stripeSessionId: session.id }, data: { status: 'paid' } }) }) ``` ### Step 4: GitHub Webhook Verification ```typescript // routes/webhooks/github.ts — GitHub webhook handler import crypto from 'crypto' import { safeEqual } from '../../lib/webhooks/verify' function verifyGitHubSignature(payload: string, signature: string, secret: string): boolean { const expected = 'sha256=' + crypto .createHmac('sha256', secret) .update(payload) .digest('hex') return safeEqual(signature, expected) // from lib/webhooks/verify.ts } export async function handleGitHubWebhook(req: Request) { const body = await req.text() const sig = req.headers.get('x-hub-signature-256') ?? '' const deliveryId = req.headers.get('x-github-delivery') // unique per delivery; use as the dedup key if (!verifyGitHubSignature(body, sig, process.env.GITHUB_WEBHOOK_SECRET!)) { return new Response('Invalid signature', { status: 401 }) } const event = req.headers.get('x-github-event') const payload = JSON.parse(body) switch (event) { case 'push': await handlePush(payload) break case 'pull_request': await handlePR(payload) break } return new Response('OK', { status: 200 }) } ``` GitHub expects a 2XX within 10 seconds on github.com, otherwise the delivery counts as failed. `X-GitHub-Delivery` is the dedup key for `processOnce`. Treat the payload as UTF-8. ### Step 5: Slack Request Verification Slack signs `v0:{timestamp}:{raw body}` with the signing secret and sends `X-Slack-Signature` (`v0=` + hex) and `X-Slack-Request-Timestamp`. Reject timestamps older than five minutes yourself, because the signature alone does not stop a replay. ```typescript // routes/webhooks/slack.ts import crypto from 'crypto' import { safeEqual } from '../../lib/webhooks/verify' export async function handleSlackRequest(req: Request) { const body = await req.text() const ts = req.headers.get('x-slack-request-timestamp') ?? '' const sig = req.headers.get('x-slack-signature') ?? '' if (!/^\d+$/.test(ts) || Math.abs(Date.now() / 1000 - Number(ts)) > 300) { return new Response('Stale request', { status: 400 }) } const expected = 'v0=' + crypto .createHmac('sha256', process.env.SLACK_SIGNING_SECRET!) .update(`v0:${ts}:${body}`) .digest('hex') if (!safeEqual(sig, expected)) return new Response('Invalid signature', { status: 401 }) return new Response('OK', { status: 200 }) } ``` ### Step 6: Keep the Raw Body (Express) `express.json()` re-serializes the body and breaks the signature. Mount the raw parser on the webhook route before any global JSON middleware: ```typescript import express from 'express' const app = express() app.post('/webhooks/stripe', express.raw({ type: 'application/json' }), (req, res) => { // req.body is a Buffer here const event = stripe.webhooks.constructEvent( req.body, req.headers['stripe-signature']!, process.env.STRIPE_WEBHOOK_SECRET!) res.sendStatus(200) }) app.use(express.json()) // after the webhook routes ``` ## Examples ### Example 1: Stripe handler returns 400 on every real event A user says: "Stripe webhooks work with `stripe trigger` but fail in production with `No signatures found matching the expected signature for payload`." The usual causes, in order: the body was parsed by `express.json()` (Step 6), the production endpoint uses the CLI's `whsec_` secret instead of the dashboard endpoint's, or a proxy rewrote the body. Fix: raw-body route, secret from `STRIPE_WEBHOOK_SECRET` for that endpoint. Result: `constructEvent` returns the event and the endpoint answers 200. ### Example 2: Retried GitHub delivery created two orders A user says: "My GitHub app opened two deployments for one push." GitHub does not redeliver failed deliveries automatically, but a person or a redelivery script can resend one, and a slow handler (over 10 seconds) is counted as failed. Dedupe on `X-GitHub-Delivery`. Wrap the handler in `processOnce(deliveryId, ...)`, return 202 immediately and do the work on a queue. Result: a repeated delivery with the same ID logs `Duplicate webhook ... skipping` and nothing runs twice. ## Guidelines - ALWAYS verify signatures before processing. Never trust unverified webhooks. - Use `crypto.timingSafeEqual` through a helper that checks lengths first; it throws on unequal lengths, which would turn a forged short header into a 500. Regular `===` leaks timing information. - Check a timestamp window (Stripe: built in, 5 min; Slack: do it yourself) in addition to deduplicating event IDs. - Respond 4xx for bad signatures and 2xx once the event is safely stored; a 5xx makes the provider retry. - Rotate secrets on leak; never log the secret or the full signature header. - Parse the raw body for verification, not JSON-parsed data (parsing may alter the payload). - Implement idempotency — webhooks are at-least-once delivery; you WILL receive duplicates. - Return 200 quickly and process asynchronously (queue) to avoid timeout retries. - Store webhook event IDs for at least as long as the provider retries (Stripe: up to three days, so 48h is too short for it) to detect replays. --- Source attribution: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/webhook-security/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Terminal Skills Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/webhook-security/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: DevOps / SRE, Backend Developer, Security Engineer Specialties: API, Backend Tools: Stripe, GitHub Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 1e2eae567ee9b1af89f39bc74a97c72e04af453b960fd074336610091fdf0e10