recon-techstack-fingerprinting
Passively identify a target's full technology stack — frontend framework, backend runtime, server, CMS, CDN/WAF, cloud, and versions — from public signals, then route to the right attack skills and CVEs. Load at the start of a web/API assessment, when choosing which techniques apply, or when "what i
v2026.10.14-ee0e0c52 instalaciones+2 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/recon-techstack-fingerprintingEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete3917b786…90a8a4a1
3917b786c507…1a6190a8a4a11 archivo · 2.3 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-techstack-fingerprinting@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When it applies
The start of any web/API engagement, before you pick techniques. Knowing the stack turns a generic
"test everything" into a targeted plan: a Rails app routes to mass-assignment and deserialization,
a GraphQL backend to api-graphql, a WAF in front changes your payloads-waf-bypass approach, and
a pinned version turns into a CVE shortlist. It is passive OSINT — public signals only, no exploit.
Why it works
Applications advertise themselves constantly: response headers, cookie names, HTML generator tags, JS bundle names, error pages, TLS certs, DNS/CDN records, public repos, and job postings all leak the stack. Cross-correlating several weak signals gives a high-confidence picture no single tool produces — and confidence is what keeps you from scoring a CVE against a wrong guess.
Method
Work outside-in, then correlate. Keep every claim tagged with the signal that supports it and a confidence level.
- Infrastructure first (asset inventory). CDN/WAF, DNS, TLS/CT logs, cloud provider, and the
domain/subdomain/IP footprint (
recon-subdomain-enum,recon-dns-analysis). This scopes everything else and often reveals origin IPs behind a CDN. - Frontend. JS frameworks and meta-frameworks (Next/Nuxt/Angular), CSS libs, build tooling,
and CMS from the DOM,
<meta name="generator">, bundle filenames, and source maps.whatweb <url>, Wappalyzer, and reading the loaded JS. - Backend. Web server, runtime/language, framework, and CMS from
Server/X-Powered-Byheaders, cookie names (PHPSESSID,JSESSIONID,_rails_session,csrftoken), default error pages, and path conventions (/wp-json,/api/v1,.aspx). - Security surface. Security headers, CSP (which reveals third-party hosts/SaaS),
security.txt, email auth (SPF/DMARC), and the WAF vendor. - OSINT. Public GitHub/GitLab repos, job postings/ATS (they name the exact stack), and the Wayback Machine for historical/leaked endpoints and migrated tech.
- Correlate. Cross-validate signals, resolve conflicts (a backported
Serverbanner vs. a framework's real version), score confidence, and produce the routing decision.
Routing (what the result feeds)
- CMS/framework identified → the matching
web-*classes (e.g. WordPress → plugin CVEs, upload; Rails/Spring → deserialization, mass assignment). - API style →
api-graphql,api-grpc,api-bola. - WAF present →
payloads-waf-bypass. - Pinned versions → CVE shortlist (enrich against the NVD), gated by real applicability, not the banner.
- Cloud/CDN →
cloud-*and origin-IP discovery.
Gotchas
- One signal is a guess; correlation is a finding. A
Server:header alone is spoofable and backported — don't route a version-specific CVE off it. Require a second corroborating signal. - CDN/WAF masks the origin — the stack you fingerprint at the edge may not be the origin's; hunt the origin IP before concluding.
- Passive means passive — no auth, no active exploitation here; that's for the domain skills
this one routes to. Stay within
tradecraft-scope-roe. - Wildcard/parked hosts and shared infra can attribute the wrong stack to a domain — confirm the host actually serves the app.
Verify success
A stack profile where each component names the signal and confidence behind it, and a concrete "test these next" list of skills + a CVE shortlist — not a raw dump of tool output.
References
Wappalyzer/WhatWeb signatures; MITRE ATT&CK T1592/T1595 (reconnaissance); NIST NVD for version→CVE.
Archivos de esta versión
- SKILL.md4.2 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 3917b786 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Reconocimiento y OSINT
Ver la categoría- gobusteraeondave/gobuster4
- ghuntaeondave/ghunt4
- stride-threat-modelingsecurityskills/stride-threat-modeling3
- attack-surface-reconsecurityskills/attack-surface-recon3
- bug-bounty-recon-pipelinesecurityskills/bug-bounty-recon-pipeline3
- implementing-attack-surface-managementmukul975/implementing-attack-surface-management3
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/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login