SkillsAdd

mn-youssef/security-skills

injection-testing

Use when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl.

First seen Jun 8, 2026

Installation

$ npx skills add mn-youssef/security-skills --skill injection-testing
View on skills.sh ↗ GitHub repository ↗

Summary

  • Use when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl. blind/time-based), OS command injection, server-side template injection (SSTI), XXE, LDAP/XPath, and CRLF/header injection.
  • Confirms on a running app what security-code-audit finds in source.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs
expo-api-routes Shared topics
expo/skills 37.9K installs
golang-dependency-injection Similar name
samber/cc-skills-golang

Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability…

36.9K installs
sqli-sql-injection Similar name
yaklang/hack-skills

>- SQL injection playbook. Use when input reaches SQL queries, authentication logic, sorting, f…

3.3K installs

Also in this package

Other skills from mn-youssef/security-skills · top by installs.

npx skills add mn-youssef/security-skills
file-upload-and-ssrf 35 pentest-reporting 35 client-side-exploitation 35 recon-and-osint 34 security-testing 34 authentication-testing 33 api-security-testing 32 vulnerability-chaining 32 active-pentest 32 access-control-testing 32

Browse all from mn-youssef/security-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 45
License LICENSE
Default branch master
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,768 B
  • docs SUMMARY.md 323 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 30 installs

SKILL.md

Injection Testing (FIND/EXPLOIT — input reaches an interpreter)

Overview

Injection happens when input crosses into a language an interpreter executes — SQL, a shell, a template engine, an XML/LDAP/XPath parser. This skill proves it dynamically; the code-level patterns live in security-code-audit/references/database.md and api-backend.md.

Core principle: Find where input changes the structure of a command, not just its data. A working injection is a tiny structural payload that changes the interpreter's behavior.

Applies when / Skip when

  • Applies when: untrusted input can reach an interpreter — SQL/NoSQL DB, OS shell, template

engine, or XML/LDAP/XPath parser.

  • Skip when: a given sink type is absent → that injection class is N/A.
  • If N/A: name the absent interpreters (e.g. "no SQL → SQLi N/A") and test only the sinks

that exist. Partial applicability is normal here.

⚠️ Authorization

Your own/authorized app, non-prod for stateful payloads. Never --dump real data, never --os-shell/RCE on shared systems, never ; DROP/destructive payloads. Confirm, don't damage.

Method

  1. Map sinks — every input that could reach a query/command/template/parser (use the audit findings).
  2. Probe — send a structure-breaking character and watch for a behavior change (error,

different result, timing).

  1. Confirm — escalate from "something changed" to a controlled, benign proof.
  2. Bound impact — note what an attacker could reach; do not exfiltrate real data.

Quick reference — probe → confirm

Type Probe Confirm (benign)
SQLi ' " ') → error/change boolean ' OR '1'='1 ; time ' OR SLEEP(5)--
Blind SQLi no output? time-based / boolean differential
NoSQLi ', {"$ne":null}, [$gt]= auth bypass via operator injection
Command ;id ` id id $(id)` out-of-band DNS, or time ;sleep 5
SSTI ${77} {{77}} <%=7*7%> render 49 → engine-specific escalation
XXE XML with external entity OOB fetch / file read (benign canary)
LDAP )(uid= filter alteration
XPath ' or '1'='1 node selection change
CRLF %0d%0a in reflected header header/response splitting

See references/injection-recipes.md for per-type detection and safe-confirmation payloads.

Tooling

sqlmap for SQLi confirmation (scoped: --batch --level/--risk low, no --dump/--os-shell), Burp/ZAP for fuzzing, OOB via an interaction server (Burp Collaborator/interactsh) for blind/XXE. Drive them via active-pentest.

Output

Per finding: the sink, the structural payload, the evidence of interpretation (error/time/OOB), and the bounded impact (e.g. "DB read possible"). High–Critical.

Hand-off

Often a foothold/escalation primitive → vulnerability-chaining; fix via security-hardening (parameterization, safe APIs, allowlists, disabling external entities, output of structure-free queries).

Common mistakes

  • Only trying SQLi — SSTI, XXE, command, NoSQL hide in templates, file parsers, search, and JSON.
  • Missing blind injection — no visible output ≠ not vulnerable; use time/boolean/OOB.
  • Going destructive to "prove it" — a SLEEP or 49 proves it; DROP is vandalism.
  • Forgetting second-order — stored input that injects when later used in a query.