web-app-attack-chain — Claude Code skill for attack analysis
web-app-attack-chain is a Claude Code skill that rebuilds a web app attack from request logs. It identifies successful in-app actions and lists the cleanup a person must handle.
Apache-2.0 ★ 71 updated 2026-11-15
npx skills add Problem99-io/kodeblue --skill web-app-attack-chain -a claude-codeWhat web-app-attack-chain does
The skill orders requests from one client into an attack sequence: reconnaissance, account creation or login, then uploads or changes to app data and settings. Response codes help locate the point where failed attempts give way to a successful request. Actions after that point are included in the investigation.
Its report tracks created accounts, issued sessions and tokens, uploaded files, and changed or exported data. The skill reads kodeblue's request log and the application's access log; host_read can retrieve their latest entries. The kodeblue log is available when the request tap is enabled. kodeblue cannot query most application databases, so the report separates evidence confirmed by logs from details a person must check in the app.
For containment, the skill calls for block_ip and a log monitor. Its handover list covers deleting accounts and uploads, revoking sessions and tokens, restoring changed data, and fixing the vulnerable endpoint. A successful login or upload can count as an attack even if the host itself was unchanged.
What it helps with
- reconstruct an attacker's request sequence
- find the request that made the attack succeed
- identify affected accounts, sessions, and uploads
- list cleanup actions that require a person
Example prompts for the agent
- Rebuild the attack from the request logs and identify the first successful request.
- Check which accounts, sessions, and files the client in the logs affected.
- Write an incident handover with the effects and the actions a person must take.
How to install web-app-attack-chain
1Skills CLI (Vercel)
npx skills add Problem99-io/kodeblue --skill web-app-attack-chain -a claude-code2Manually: put the files in place
~/.claude/skills/web-app-attack-chain/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/web-app-attack-chain/
1Skills CLI (Vercel)
npx skills add Problem99-io/kodeblue --skill web-app-attack-chain -a codex2Manually: put the files in place
.agents/skills/web-app-attack-chain/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Problem99-io/kodeblue --skill web-app-attack-chain -a cursor2Manually: put the files in place
.cursor/skills/web-app-attack-chain/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Problem99-io/kodeblue blue/skills/web-app-attack-chain2Manually: put the files in place
.github/skills/web-app-attack-chain/SKILL.md1Skills CLI (Vercel)
npx skills add Problem99-io/kodeblue --skill web-app-attack-chain -a gemini-cli2Platform CLI
gemini skills install https://github.com/Problem99-io/kodeblue --path blue/skills/web-app-attack-chainManually: put the files in place
.devin/skills/web-app-attack-chain/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about web-app-attack-chain
How do I install web-app-attack-chain in Claude Code?
Run npx skills add Problem99-io/kodeblue --skill web-app-attack-chain -a claude-code. The skill file is installed at ~/.claude/skills/web-app-attack-chain/SKILL.md.
What does web-app-attack-chain do?
It rebuilds a web application attack from request logs, finds the successful step, and reports its effects inside the app. It also lists follow-up actions that require a person.
Does the skill need access to the application database?
The skill uses kodeblue's request log and the application's access log, but kodeblue cannot query most application databases. A person must check app-level details that the logs cannot confirm.
Source text
SKILL.md · Apache-2.0
--- name: web-app-attack-chain description: Reconstruct an attack on a web application from its request log — probing, sign-up and login, upload or admin abuse — find what the attacker achieved inside the app, and list what only a human can undo. metadata: kodeblue-bundled: true --- # Web application attack chains Attacks on an application often never touch the host: the attacker signs up, logs in, uploads, changes data. The request log is the evidence. Use kodeblue's request log (`/var/lib/kodeblue/requests/access.log`, when the request tap is on) and the application's own access log; `host_read` with a negative offset reads the end of either. ## 1. Rebuild the chain Filter by the client address and put the requests in order. Scripted attacks show a steady rhythm (a request every few seconds) and a tool user agent (`curl`, `python-requests`, `Python-urllib`, `Go-http-client`, `sqlmap`, `nuclei`). Typical steps: 1. **Recon**: version, admin, config or API-listing endpoints, `/.git`, `/.env`, directory guessing (many 404s). 2. **Foothold**: account creation (`POST` to a users or register endpoint → 201), login (→ 200 with a token or session cookie), password reset abuse. 3. **Abuse**: uploads, profile or settings changes, admin actions, order or payment tampering, data export, injection payloads in parameters. ## 2. Find the moment it worked Probing fails until it does not. The status codes tell you when: a run of 4xx or 5xx on an endpoint followed by 2xx (`410`/`500` on an upload, then `204`) is the success. Everything after that moment is in scope. A successful upload can write outside the upload directory: check the drop zones the service can write (see `service-process-exploitation`). ## 3. Scope what the attacker holds inside the app List every application-level foothold, because blocking the address does not remove them: - accounts created (time, from which request) and accounts logged into, - sessions or API tokens issued, password or email changes, - uploaded files and where they were stored, - data changed (profiles, orders, settings) or exported. kodeblue cannot query most application databases. Say which of these you could confirm and which a human must check in the application. ## 4. Contain and hand over - `block_ip` on the client as soon as the chain shows success (see `containment-verification` for checking it holds). A blocked attacker often returns from the same address after a restart, or from a new one with the same rhythm and user agent: a `log` monitor on the request log for that client, or for the first hit on sensitive endpoints, catches the return. - The human's list, in the report: delete attacker accounts, revoke their sessions and tokens, remove uploads, restore changed data, and fix the vulnerable endpoint. Name the endpoint and the request that succeeded. ## Verdict A client that probes and then succeeds at account creation, login, upload or an admin action without being a known user or test client in the access model is a true_positive, even when nothing changed on the host.
© Problem99-io · Apache-2.0 · Problem99-io/kodeblue