competition-bundle-sourcemap-recovery

Reconstruct minimal runtime graphs from served frontend assets and source maps.

4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-bundle-sourcemap-recovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-bundle-sourcemap-recovery
Source: https://github.com/xjtu-wang/DigAgent/tree/main/.agents/skills/competition-bundle-sourcemap-recovery
Command: npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-bundle-sourcemap-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables security researchers to reconstruct the runtime structure behind served frontend assets by analyzing bundles, source maps, and manifests to reveal how a site executes in production.

Core Features & Use Cases

  • Reconstructs the minimal runtime graph from served assets including entry HTML, bootstrap bundles, and chunk maps.
  • Maps asset-to-runtime relationships using source maps and manifests to explain runtime behavior in a controlled sandbox.
  • Use Case: After establishing a ctf-sandbox context, inspect built frontend artifacts to identify hidden routes or APIs.

Quick Start

Observe the served asset set and generate a minimal runtime graph by tracing bootstrap loaders and source maps.

Frequently Asked Questions about competition-bundle-sourcemap-recovery

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

FAQPage Schema
How do I recover hidden routes and APIs from served frontend bundles?

Reconstructing runtime from source maps involves tracing bootstrap loaders and chunk maps to map asset-to-runtime relationships, producing a minimal runtime graph that explains how production frontend assets execute in a controlled sandbox.

What is the best way to map asset-to-runtime relationships using source maps and manifests?

The best way to map asset-to-runtime relationships is by analyzing entry HTML, bootstrap bundles, and chunk maps alongside source maps to establish a precise asset-to-runtime mapping and produce a minimal runtime graph.

Can I trace bundle loading behavior in a controlled sandbox without source code?

Yes, you can trace bundle loading without source code by observing the served asset set, extracting source maps and chunk maps, and tracing bootstrap loaders to reconstruct the frontend runtime structure from built artifacts.

Do I need a sandbox orchestrator to reconstruct runtime structure from frontend artifacts?

Yes, a ctf-sandbox orchestrator must establish context first. This skill applies after the sandbox is ready, using the controlled environment to safely inspect served assets, source maps, and manifests for runtime reconstruction.

What limitations exist when reconstructing runtime graphs from chunk maps and bootstrap loaders?

Reconstructing runtime graphs is limited by the availability of source maps and manifests on the served assets. If source maps are stripped or chunk maps are inaccessible, generating a precise minimal runtime graph becomes significantly harder.