Back to catalog
Static reviewDevelopment

Skill dossier

exploiting-excessive-data-exposure-in-api

Source declaration

Tests APIs for excessive data exposure (OWASP API3:2023) by intercepting raw API responses and comparing them against what the UI actually renders, looking for leaked PII, internal identifiers, debug data, or business-sensitive fields the frontend filters but the API still transmits. Use when auditing REST or mobile-app APIs for over-fetching, response filtering bypass, or unintended data leakage in endpoint responses.

The author's original description, preserved in English. It describes intent, not verified performance.

Tests APIs for excessive data exposure (OWASP API3:2023) by intercepting raw API responses and comparing them against what the UI actually renders, looking for leaked PII, internal identifiers, debug data, or business-sensitive fields the frontend filters but the API still transmits. Use when auditing REST or mobile-app APIs for over-fetching, response filtering bypass, or unintended data leakage in endpoint responses.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Tests APIs for excessive data exposure (OWASP API3:2023) by intercepting raw API responses and comparing them against what the UI actually renders, looking for leaked PII, internal identifiers, debug data, or business-sensitive fields the frontend filters but the API still transmits. Use when auditing REST or mobile-app APIs for over-fetching, response filtering bypass, or unintended data leakage in endpoint responses. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L57]
  • Step 1: Response Schema Discovery [Source statement; provisional, not tested. Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L59]
  • Step 2: Sensitive Data Pattern Detection [Source statement; provisional, not tested. Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L101]
  • Step 3: Compare UI Display vs API Response [Source statement; provisional, not tested. Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L164]
  • Step 4: Test User Object Exposure in Related Endpoints [Source statement; provisional, not tested. Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L199]
  • Step 5: GraphQL Over-Fetching Analysis [Source statement; provisional, not tested. Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L225]
  • Step 6: Debug and Internal Data Leakage [Source statement; provisional, not tested. Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L278]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L1-L32]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
34.5 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/exploiting-excessive-data-exposure-in-api/LICENSEOther11 KB
skills/exploiting-excessive-data-exposure-in-api/references/api-reference.mdReference2.2 KB
skills/exploiting-excessive-data-exposure-in-api/scripts/agent.pyScript5.6 KB
skills/exploiting-excessive-data-exposure-in-api/SKILL.mdInstruction15.8 KB

SKILL.md frontmatter

{
  "name": "exploiting-excessive-data-exposure-in-api",
  "description": "Tests APIs for excessive data exposure (OWASP API3:2023) by intercepting raw API responses and comparing them against what the UI actually renders, looking for leaked PII, internal identifiers, debug data, or business-sensitive fields the frontend filters but the API still transmits. Use when auditing REST or mobile-app APIs for over-fetching, response filtering bypass, or unintended data leakage in endpoint responses.",
  "domain": "cybersecurity",
  "subdomain": "api-security",
  "tags": [
    "api-security",
    "owasp",
    "data-exposure",
    "rest-security",
    "pii-leakage"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "ID.RA-01",
    "PR.DS-10",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1190",
    "T1059.007",
    "T1552.001",
    "T1027",
    "T1070"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Response Schema Discovery

    Source-described action candidate under “Step 1: Response Schema Discovery”; not verified execution.

  4. 04
    Action

    Step 2: Sensitive Data Pattern Detection

    Source-described action candidate under “Step 2: Sensitive Data Pattern Detection”; not verified execution.

  5. 05
    Output

    Step 3: Compare UI Display vs API Response

    Source-described output candidate under “Step 3: Compare UI Display vs API Response”; not verified execution.

  6. 06
    Action

    Step 4: Test User Object Exposure in Related Endpoints

    Source-described action candidate under “Step 4: Test User Object Exposure in Related Endpoints”; not verified execution.

Inspect all extracted workflow candidates (19 candidate steps)
  1. 07
    Action

    Step 5: GraphQL Over-Fetching Analysis

    Source-described action candidate under “Step 5: GraphQL Over-Fetching Analysis”; not verified execution.

  2. 08
    Action

    Step 6: Debug and Internal Data Leakage

    Source-described action candidate under “Step 6: Debug and Internal Data Leakage”; not verified execution.

  3. 09
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Action

    Configure mitmproxy on a test device and authenticate as the test user

    Source-described action candidate under “Scenario: Mobile Banking API Data Exposure Assessment”; not verified execution.

  7. 13
    Action

    Capture all API responses during a complete user session (login, view accounts, transfer, logout)

    Source-described action candidate under “Scenario: Mobile Banking API Data Exposure Assessment”; not verified execution.

  8. 14
    Action

    Analyze `GET /api/v1/accounts` response: UI shows 4 fields but API returns 23 fields

    Source-described action candidate under “Scenario: Mobile Banking API Data Exposure Assessment”; not verified execution.

  9. 15
    Action

    Discover that the API returns `routingnumber`, `accountholderssnlast4`, `internalriskscore`, `kycverificationstatus`, and `linkedexternalaccounts` - none shown in UI

    Source-described action candidate under “Scenario: Mobile Banking API Data Exposure Assessment”; not verified execution.

  10. 16
    Action

    Analyze `GET /api/v1/transactions` response: API returns `merchantid`, `terminalid`, `authorizationcode`, `processorresponse` fields not needed by the client

    Source-described action candidate under “Scenario: Mobile Banking API Data Exposure Assessment”; not verified execution.

  11. 17
    Action

    Check `GET /api/v1/users/me`: API returns `lastloginip`, `mfabackupcodesremaining`, `accountofficername`, and `creditscoreband`

    Source-described action candidate under “Scenario: Mobile Banking API Data Exposure Assessment”; not verified execution.

  12. 18
    Action

    Test error responses: `POST /api/v1/transfers` with invalid payload returns SQL table name in error message

    Source-described action candidate under “Scenario: Mobile Banking API Data Exposure Assessment”; not verified execution.

  13. 19
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

23 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

15 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 15 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

8 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/exploiting-excessive-data-exposure-in-api/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/exploiting-excessive-data-exposure-in-api/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/exploiting-excessive-data-exposure-in-api
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.