info-disclosure-hunter

Detect sensitive data exposure through serialization drift, public artifacts, and cross-origin resources.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill info-disclosure-hunter-maybe4a6f7365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: info-disclosure-hunter
Source: https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework/tree/main/skills/info-disclosure-hunter
Command: npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill info-disclosure-hunter-maybe4a6f7365

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests.

What problem does it solve? Bug bounty researchers need a systematic way to find information disclosure vulnerabilities—leaked tokens, PII, hidden JSON fields, and exposed CI logs—without over-claiming or violating program rules. This Skill provides a structured hunting method with verified negative controls so findings are real, in-scope, and reportable. ## Core Features & Use Cases - Serialization Drift Testing: Diff HTML, JSON, GraphQL, export, and print representations of the same object to find fields the requesting identity should not receive. - Public Artifact & Log Sweep: Inspect CI logs, bot-created repositories, source maps, and build artifacts for active secrets, then confirm with read-only identity endpoints only. - Cross-Origin & Parser Isolation Tests: Detect authenticated data in dynamic JavaScript (e.g., service workers) and memory leakage through file preview/conversion pipelines using canary uploads. - Negative-Control Taxonomy: Apply 12 stop-condition categories grounded in real HackerOne report outcomes to avoid filing duplicates, expected behavior, or below-threshold findings. - Use Case: While testing a target's report endpoint, request its .json variant with a low-privilege token, diff field names against the authorized UI, and discover internal reporter attributes—then redact and report with evidence. ## Quick Start Ask the agent to test a target object's JSON and GraphQL representations for fields beyond what a low-privilege account should see, using the info-disclosure hunting method.

Frequently Asked Questions about info-disclosure-hunter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test for information disclosure vulnerabilities in a web app?

Request the same object through multiple representations—HTML, .json, GraphQL, export, and print views—with a low-privilege account, then diff field names against the authorized UI contract. A leak is confirmed only when a field appears that the test identity should not receive.

How to find leaked API tokens in CI logs and public repositories?

Search known project and account names in public CI logs, bot-created repositories, and commit history for secret-shaped patterns. Validate candidates only against read-only identity endpoints, stop after scope confirmation, and request rotation.

What counts as a reportable information disclosure in bug bounty programs?

A finding must be technically vulnerable, in scope, and above the program's impact threshold—evaluated as three separate decisions. Exposed usernames, public metadata, or intentionally public files typically fall below the threshold and should not be filed.

Can a service worker or JavaScript file leak user data cross-origin?

Yes, if a script resource like sw.js varies its body based on authentication cookies, classic script inclusion can expose identifiers to an unrelated origin. Confirm by comparing the resource with and without a controlled authenticated cookie.

What are the limits of canary-based memory disclosure testing?

Upload one or two benign files containing a unique canary and inspect only the generated preview for bytes you never supplied. Random image corruption alone is not disclosure, and high-volume reproduction attempts violate testing norms.