Skip to content
cccskills
FreePublished on GitHub

techstack-backend

Backend tech-stack identification — web servers, runtimes, languages, frameworks, databases, APIs, and CMS via HTTP headers, cookies, error pages, and API discovery.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595 stars(GitHub 595 + cccskills 0)

Run score Not tested

See how to install

Files included (2)

  • SKILL.md1.5 KB
  • reference/patterns.md5.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Backend Tech-Stack Identification

Scope

Identify server-side technologies: web servers (nginx, Apache, IIS), runtimes (Node, Python, PHP, Ruby, Java, .NET), backend frameworks (Express, Django, Flask, Rails, Laravel, Spring, ASP.NET), databases (Postgres, MySQL, Mongo, Redis), CMS (WordPress, Drupal, Magento), and API surfaces (REST, GraphQL, OpenAPI).

Signals (input)

  • HTTP response headers — Server, X-Powered-By, X-AspNet-Version, X-Drupal-*, X-Generator, etc.
  • Cookies — session-name fingerprints (PHPSESSID, JSESSIONID, _rails_session, ...)
  • Error page bodies (404, 500)
  • Path patterns hinting CMS (/wp-admin/, /sites/default/)
  • API subdomains and OpenAPI/Swagger/GraphQL endpoints
  • robots.txt directives

Inferences (output)

  • Web server + version
  • Runtime / language + version
  • Backend framework (with implied runtime)
  • CMS + version
  • Database (often indirect — via ORM dependency or hosted-DB DNS)
  • API style (REST/GraphQL/gRPC) and authentication scheme

Techniques

See reference/patterns.md.

When to use

  • Phase 2/3 of a tech-stack OSINT engagement
  • Mapping server-side attack surface (RCE, SSRF, deserialization)
  • CVE matching by server + version
  • Locating GraphQL / OpenAPI for follow-on api-security testing

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Offensive AI security testing and exploitation framework. Systematically tests LLM applications for OWASP Top 10 vulnerabilities including prompt injection, model extraction, data poisoning, and supply chain attacks. Integrates with pentest workflows to discover and exploit AI-specific threats.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

API security testing - GraphQL, REST API, WebSocket, and Web-LLM attack techniques.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Stitches confirmed single-asset findings into multi-hop attack paths across the organization. Builds a graph where nodes are assets and edges are confirmed exploit hops citing the findings that enable them.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Acquire an authenticated session THROUGH MFA/OTP on an in-scope target and emit a reusable session artifact (Playwright storageState + Bearer) so executors can test the post-auth attack surface. Use when the highest-value authenticated classes (BOLA/IDOR/mass-assignment/injection on the real data APIs) are blocked because login is gated by SMS-OTP or TOTP MFA. Distinct from the authentication skill (which ATTACKS auth); this one legitimately authenticates and hands the session to the rest of the engagement.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Authentication security testing - auth bypass, JWT attacks, OAuth flaws, password attacks, 2FA bypass, CAPTCHA bypass, and bot detection evasion.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Smart contract security testing and blockchain CTF exploitation. Covers Solidity vulnerability analysis, EVM storage manipulation, delegatecall attacks, CREATE/CREATE2 address prediction, and common DeFi exploit patterns. Use when analyzing Solidity contracts, solving blockchain challenges, or testing smart contract security.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

See all skills by transilienceai

Report a problem with this skill