Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
noorqureshi/tools-curlWeb y bug bounty

tools-curl

⁨Use curl as the ground-truth HTTP client during recon and verification — browser-impersonation headers for CDN/WAF 403s, --globoff for bracket params, Windows curl.exe quirks, SPA false-200 traps. Load when bare tooling gets 403/blocked at a CDN edge, an API needs precise hand-crafted requests, or s⁩

v2026.10.14-ee0e0c53 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/tools-curl

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
rE+18ROYpS…4fzhSMDw==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete4316de34…ead5ad98
4316de344c21…b7d6ead5ad981 archivo · ⁦2.4 KB⁩
EscaneoMedio2 hallazgos
  • injection.no_confirmationSKILL.md:74
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/tools/tools-curl@ee0e0c5

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

When it applies

Any time you need to know what a server actually returns — no proxy magic, no scanner interpretation — or when automated tooling is being blocked at a CDN/WAF edge and you suspect the request shape, not the content, is the problem. Typical trigger: bare curl or a datacenter UA gets 403 with a JSON access-policy body or a CF-RAY header, while the same endpoint works in a real browser.

Why it works

Edge protection (Cloudflare & friends) classifies clients by TLS/HTTP fingerprints and headers. A request carrying a browser User-Agent plus plausible Origin/Referer/Sec-Fetch-* headers often sails through where a naked curl gets challenged — and unlike a scanner, curl shows you the exact bytes that came back.

Method

  1. Baseline: curl -sS -D - -o /dev/null --max-time 15 https://target/ — -D - dumps response headers, -o /dev/null discards the body, --max-time keeps a hung endpoint from stalling you.
  2. On an edge 403, impersonate the browser before concluding anything:
    bash
    curl -sS --max-time 15 \
      -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36" \
      -H "Accept: application/json, text/plain, */*" \
      -H "Origin: https://app.example" \
      -H "Referer: https://app.example/" \
      -H "Sec-Fetch-Site: same-site" -H "Sec-Fetch-Mode: cors" -H "Sec-Fetch-Dest: empty" \
      "https://api.example/v1/health"
    Match Origin/Referer to the site's real front-end origin — that's usually what the policy keys on.
  3. Bracket/query params (prototype-pollution shapes) need --globoff: curl treats [] as URL globs and dies with curl: (3) bad range in position N. Either:
    bash
    curl --globoff -sS "https://target/?__proto__%5Btest%5D=polluted"
    curl --globoff -sS -G "https://target/path" --data-urlencode "__proto__[test]=polluted"
  4. Read the response like a signal, not a verdict:
    • 403 + JSON access-policy / CF-RAY → retry with browser headers (step 2).
    • Still 403 and HTML contains Cf-Mitigated: challenge → a real browser or an authenticated session is required; do not brute-force the edge.
    • SPA route that returns 200 with an identical body size for every path → front-end router, not a real API hit — don't log it as an endpoint.
  5. Feed curl requests to other tools: once a request works, export/replay it exactly — save it for sqlmap -r (tools-sqlmap) or send it to Burp Repeater (tools-burp-suite) instead of re-deriving it.

Gotchas

  • curl -I sends HEAD — some apps 405 or behave differently on HEAD; for a real GET with headers shown, use curl -s -o /dev/null -D -.
  • Windows curl.exe vs the alias — in PowerShell curl may be an alias for Invoke-WebRequest; call curl.exe explicitly, and remember --globoff for [].
  • Windows httpx collision — the httpx command may resolve to the Python httpx library CLI, not ProjectDiscovery's httpx; check httpx -version before piping recon output into it.
  • A working browser-header bypass is recon, not a bypass finding — it means the edge admits browser-shaped traffic; record it and continue, don't report it.
  • Timeouts are part of the command — always --max-time; a hung curl in an automated loop silently stalls the whole pipeline.

Verify success

You have a reproducible, copy-pasteable request that returns the expected status/body through the edge, saved verbatim in the engagement notes so any later tool (sqlmap, Repeater, a finding's repro steps) uses the exact same bytes.

References

curl manual (--globoff, --data-urlencode); Cloudflare edge behavior. Pipeline context: automation-recon-pipeline.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaPrompt injection · injection.no_confirmationSKILL.md:74
  2. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.10.14-ee0e0c513 nov 2026ee0e0c54316de34Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login