How do I install the Hunt Xxe skill?

Run npx skillmds@latest add duriantaco/hunt-xxe in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hunt Xxe safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hunt Xxe?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hunt Xxe free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hunt Xxe?

duriantaco (@duriantaco) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hunt Xxe by duriantaco — Agent Skill

Name: Hunt Xxe
Author: duriantaco

Hunt Xxe

Investigate authorized XML external entity and XML parser boundaries. Use when typed discovery identifies XML or SOAP request bodies, document imports, XML or SVG uploads, DOCTYPE handling, entity-resolution behavior, parser errors, or a suspected external-entity primitive.

duriantaco ec04d7e 2 files · 1.7 KB Updated Sep 17, 2026

File contents

Hunt XML Entity Boundaries

Treat this card as advisory prioritization. XML syntax, parser errors, and DOCTYPE support are not proof of entity resolution.

Workflow

Preserve a well-formed, target-observed XML request as the baseline.
Pair a bounded entity candidate with a same-shape unresolved control. A native result without that replay remains an exploit primitive, not a verified vulnerability.
Use xxe_boundary; use file_fetch_parser only for a typed upload or import. Its fixed local-file candidates must all be authorized.
Separate parsing, resolution, readback, and outbound behavior. Preserve redacted controls and evidence references, and report validated vulnerabilities without requiring a challenge artifact.

Evidence Gate

Confirm only replayable entity-derived readback or a controlled interaction absent from the paired control. Reflected declarations, accepted syntax, errors, and timing remain observations. Keep any contract_missing result suspected rather than promoting it.

Stop Conditions

Stop without a typed parser, replay, unambiguous control, or policy budget. Do not add entity bombs, file targets, or out-of-band services beyond the authorized native set.

Frequently asked questions