smartworldarafath/rea_skill

payloads-scm-exposure

Insecure Source Code Management (SCM) can lead to several critical vulnerabilities in web applications and services.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/smartworldarafath/rea_skill --skill payloads-scm-exposure

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Source Code Management Exposure Payloads

Source: PayloadsAllTheThings/Insecure Source Code Management Category: payloads-research | Skill ID: payloads-scm-exposure

Overview

SCM exposure payloads for .git, .svn, and .hg directory disclosure and source code extraction.

This skill integrates the full PayloadsAllTheThings (PATT) payload library for the Source Code Management Exposure Payloads domain into the REA_Skill framework. Use it during authorized penetration testing, bug bounty research, security audits, and CTF challenges.

Workflow

1. Recon & Identification

  • Identify the target technology stack and injection points
  • Enumerate endpoints, parameters, and input vectors
  • Determine applicable payload categories from the reference below

2. Payload Selection

  • Browse the PATT payload library for the attack class
  • Select encoding-appropriate payloads for the target environment
  • Consider WAF bypass variants and obfuscation techniques

3. Exploitation (Authorized Only)

  • Test payloads in order: passive → active → escalation
  • Document every payload tested and its response
  • Capture PoC evidence (screenshots, HTTP logs, curl output)

4. Verification & Reporting

  • Confirm the vulnerability with a clean minimal PoC
  • Map findings to CVE/CWE where applicable
  • Report with remediation recommendations and code fixes

Full PATT Reference

Insecure Source Code Management

Insecure Source Code Management (SCM) can lead to several critical vulnerabilities in web applications and services. Developers often rely on SCM systems like Git and Subversion (SVN) to manage their source code versions. However, poor security practices, such as leaving .git and .svn folders in production environments exposed to the internet, can pose significant risks.

Summary

Methodology

Exposing the version control system folders on a web server can lead to severe security risks, including:

  • Source Code Leaks : Attackers can download the entire source code repository, gaining access to the application's logic.
  • Sensitive Information Exposure : Embedded secrets, configuration files, and credentials might be present within the codebase.
  • Commit History Exposure : Attackers can view past changes, revealing sensitive information that might have been previously exposed and later mitigated.

The first step is to gather information about the target application. This can be done using various web reconnaissance tools and techniques.

  • Manual Inspection : Check URLs manually by navigating to common SCM paths.
  • Git: http://target.com/.git/
  • SVN: http://target.com/.svn/
  • Automated Tools : Refer to the page related to the specific technology.

Once a potential SCM folder is identified, check the HTTP response codes and contents. You might need to bypass .htaccess or Reverse Proxy rules.

The NGINX rule below returns a 403 (Forbidden) response instead of 404 (Not Found) when hitting the /.git endpoint.

ps1
location /.git {
  deny all;
}

For example in Git, the exploitation technique doesn't require to list the content of the .git folder (http://target.com/.git/), the data extraction can still be conducted when files can be read.

Labs

References


REA MCP Integration

javascript
// REA MCP — Automated payload injection via REA tools
// Use analyze_function, procedure_pseudo_code, or observe_native_calls
// to identify injection sinks, then apply payloads from this skill.

Legal Notice

⚠️ Authorized Use Only. All payloads in this skill are for security research, penetration testing with written permission, CTF competitions, and defensive study. Unauthorized use against systems you do not own or have explicit permission to test is illegal.
from this repository

More skills

All skills
smartworldarafath
Community

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

1h installs
2
GitHub stars
5
Updated
Nov 8
smartworldarafath
Community

agent-reach

Read-only access to internet platforms (Twitter/X, Reddit, YouTube subtitles, GitHub, LinkedIn, Bilibili, web). Use when the agent needs to search, read web links, retrieve social discussions, CVE/vulnerability intel, or when standard web search/fetch is blocked or insufficient.

1h installs
2
GitHub stars
5
Updated
Nov 8
smartworldarafath
Community

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

1h installs
2
GitHub stars
5
Updated
Nov 8
smartworldarafath
Community

anti-ai-slop-writing

Produces human-sounding text that avoids detectable AI writing patterns. Activates on any writing task — tweets, emails, articles, bios, captions, reports, copy, messages, LinkedIn posts, cover letters, README files, or any content where the output must not read as AI-generated. Enforces banned vocabulary, structural variety, punctuation discipline, accuracy rules, and voice calibration. Use when the user says "write," "draft," "rewrite," "make this sound human," "anti-slop," "not AI," or any va

1h installs
2
GitHub stars
5
Updated
Nov 8