Commit Graph
919 Commits
Author SHA1 Message Date
Coff0xc 59cd4385ec fix(agent): frame RSI lessons in the data envelope
Lesson text was dumped straight into the system prompt. Same nonce
envelope as the other derived fields now.
2026-11-17 12:56:19 +00:00
BaaRai 278de8b2e0 Merge pull request #268 from liuxiaobo0920/fix/report-finding-quality
feat(report): surface finding proof strength in the report and the export
2026-11-17 02:09:01 +01:00
BaaRai 4e4e25f74a Merge pull request #275 from BaaRai/chore/repo-hygiene
chore: stop ignoring docs/
2026-11-17 01:50:41 +01:00
Xiaobo a0adc209ad feat(report): surface finding proof strength in the report and the export
The task report and the findings export asserted every finding with no
qualification: nothing said how far exploitation actually reached (PoE level),
whether the claim was machine-verified (verification status and note), whether
counterevidence was recorded, or whether any traffic was bound. The web UI
badges all of it (VERIFICATION_META, the detail page), so the report — the
artifact a client actually reads — was the last surface still asserting bare
claims.

Render it from one place:

- report/quality.go (new): two constructors and two pure renderers, no I/O, no
  DB handle, so the block is unit-tested without a database.
- Both surfaces call the same helpers, which is the point: the task report and
  the per-finding export cannot drift apart the way duplicated formatting does.
- Missing is explicit: a finding node with no standalone row prints
  "not assessed (no finding record)" instead of an invented zero — the honest
  gap the existing coverage work (#207) also insists on.
- Labels match the shipped UI wording (Verification, Confidence rationale,
  Counterevidence) and states are humanised ("Not assessed", "False positive"),
  with an unrecognised value printed verbatim so a new state cannot silently
  vanish from a report.
- Bound-traffic count appears once per document: as a Proof bullet in the task
  report (it has no traffic section), and in the export only when nothing is
  bound — otherwise the traffic section already states it.
- The detailed report is capped at 8 KiB in the task report only, rune-safe, with
  the cap derived into the truncation message; the export is the canonical
  per-finding document and is never silently shortened.
- The export keeps its document structure: the single-finding document gets
  "## Detailed Report" (a section like its siblings), the multi-finding summary
  gets a bold label.

Read paths only: no change to the write side of poe_level or verification_status,
no schema change (all five columns already exist), no API/DTO change (the widened
FindingMeta stays internal to the report path, and the findings list keeps
selecting only what it renders). One extra task-scoped query on GET /api/report,
because findings bodies stay off the list path.

docs/vulnerability-traffic-evidence.md §Export describes the new Markdown.
2026-11-17 08:40:37 +08:00
BaaRai 9f827577ff chore: stop ignoring docs/
The entry contradicted the four documentation files that are tracked, and any
tool that honours .gitignore concluded that docs/ does not exist. The triage
bot did exactly that on issue #271 and told a contributor the directory was
missing.

Removing it changes nothing for the tracked files and makes a genuinely
untracked file under docs/ visible in git status, which is the point.
2026-11-17 01:38:10 +01:00
BaaRai f9a35194b2 Merge pull request #266 from BaaRai/feat/traffic-replay-tab
feat(web): Replay tab in the traffic detail
2026-11-17 01:21:32 +01:00
BaaRai 515ff301f5 Merge pull request #274 from BaaRai/fix/triage-bot-context
fix(ci): give the triage bot a directory map instead of a truncated file list
2026-11-17 01:17:35 +01:00
BaaRai 524d1f70be fix(ci): give the triage bot a directory map instead of a truncated file list
repo_context() printed the first 120 tracked paths alphabetically, which
stopped at config/ on an 846-file tree, so the model never saw docs/ or
scripts/ and told a contributor on issue #271 that neither directory exists.

The summary now lists the root files, every top-level directory with its file
count, the second level, and the workflow, migration, docs and script paths.
Both prompts also state that the summary is not a listing, so a path missing
from it is never reported as a path that does not exist.

scripts/test-bot-context.sh guards the invariant in the shell CI job: every
top-level directory must appear in the summary. It fails against the previous
version, which is the point.
2026-11-17 01:07:07 +01:00
BaaRai 7cb8e9a3f4 Merge pull request #273 from BaaRai/feat/traffic-rewrite-p33a
feat(traffic): store, validate and compile capture-proxy rewrite rules
2026-11-17 01:04:13 +01:00
BaaRai e678c4e71d ci: run the rewrite-rule engine under the race detector
./traffic/rewrite joins the go test -race list of the go job.
2026-11-17 00:12:09 +01:00
BaaRai 8474131ba2 fix(server): match a kept sensitive value on type, header name and regex
A sensitive action sent without its value took the stored value at the same
position, so two sensitive actions of the same type and header name swapped
their values when reordered. The stored action is now found by type,
canonical header name and regex, wherever it stands, and exactly one must
match: none or several is refused (400, send the value).

The CRUD test no longer expects a refusal for a reordered action.
2026-11-17 00:12:09 +01:00
BaaRai 97f081ed63 fix(server): refuse a host change while a stored sensitive value is kept
An update that keeps the stored value of a sensitive action can no longer
change the rule's host matcher (compared case-insensitively): the value
would otherwise be written to a new destination. Same invariant as the
custom HTTP tools. The url_regex matcher is not compared, an accepted and
documented limit.
2026-11-17 00:12:09 +01:00
BaaRai 38d66d83b2 docs: describe the capture-proxy rewrite rules
Rule model, validation, limits, sensitive actions, API and storage, with the
statement that the proxy does not apply the rules yet. The README lists the
rules among the secrets encrypted at rest.

docs/ is ignored by .gitignore; the new file is force-added like the three
documents already tracked there.
2026-11-17 00:12:09 +01:00
BaaRai 7a9b4fdf76 feat(server): rewrite-rule API and compiled snapshot for the proxy
GET, POST, PUT and DELETE /api/traffic/rewrite-rules and
POST /api/traffic/rewrite-rules/{id}/toggle manage the rules behind
requireAuth. A rule is validated on save (400), created disabled, and
validated again before the toggle enables it. The value of a sensitive action
is never returned; an update sent without it keeps the stored value when the
stored rule has a sensitive action of the same type and header name at the
same position.

The manager compiles the enabled rules after traffic.Open and after every
change, and publishes the snapshot with Traffic.SetRewriteRules, an atomic
swap. An enabled rule the validation refuses is left out and reported as
load_error.

The proxy stores the snapshot and does not apply it: a test sends the same
request with and without matching rules and compares what the target
receives, what the client receives and what is recorded.
2026-11-17 00:12:09 +01:00
BaaRai 2613c50363 feat(db): store capture-proxy rewrite rules, sealed at rest
Migration 0005 creates traffic_rewrite_rules. The matchers and actions
columns are two JSON secret columns of db/secrets.go: InitSecrets, which runs
after the migrations, checks the key against them and encrypts any plaintext
row, as it does for the existing columns.

The CRUD lists rules in execution order and enforces 100 rules, 50 of them
enabled, under a table lock so concurrent writers cannot pass a limit.
UpdateTrafficRewriteRule hands the stored rule to an edit callback inside the
transaction, which is where a caller keeps a value it was not sent.

InitSecrets also derives the sub-key that fingerprints sensitive values in
the rewrite trace (HMAC-SHA256 of "artex-traffic-trace" under the secret key).
2026-11-17 00:12:09 +01:00
BaaRai 7c74366a44 feat(traffic): add the rewrite-rule engine as a pure package
traffic/rewrite holds the rule model of the capture proxy's rewrite rules,
their save-time validation, an immutable compiled snapshot and the
transformation of one request or response. It imports the standard library
only, so both server and traffic can use it.

Rules run by priority ascending then id ascending, as a pipeline; within a
rule the actions run in a fixed order. A rule is atomic and fails open: a
failing action or a panic cancels that rule only. A rule that needs a body it
cannot touch (binary, over 1 MiB, compressed, streamed, absent by protocol)
is skipped whole. The engine never writes to the URL, headers or bodies it is
given.

Apply returns the trace lines of the phase: the rule snapshot once per rule,
the body of the last body action only, and no value for a sensitive action or
for a field one wrote earlier in the phase. A sensitive value is fingerprinted
with HMAC-SHA256 truncated to 128 bits, or not at all without a key.

Nothing calls the engine from the proxy yet.
2026-11-17 00:12:09 +01:00
BaaRai 3f5b886b47 Merge pull request #272 from BaaRai/fix/llm-rotation-followups
fix(llm-rotation): precise exhaustion wording and binding check state
2026-11-17 00:01:12 +01:00
BaaRai 0caa9bece4 fix(llm-rotation): precise exhaustion wording and binding check state
Follow-up to #270 by @Toys0125:

- README: an intent pinned to an exhausted profile falls back to the task's
  current profile instead of retrying it, and saving the chain does not reset
  the rotation cursor.
- api.ts: the update response carries llm_rotate.
- TaskLLMProfileChain: keep a failed worker-binding lookup separate from the
  initial load, which flashed the "could not be checked" warning.
2026-11-16 23:53:22 +01:00
BaaRai 4df6ed2678 Merge pull request #270 from Toys0125/feat/multi-llm-worker-rotation
Enable concurrent multi-LLM worker rotation in task controls
2026-11-16 23:53:08 +01:00
Toys0125 d18b841a70 feat: expose concurrent multi-LLM worker rotation 2026-11-16 15:31:47 -06:00
BaaRai 7d87953d9a fix(web): disable replay when only the body preview is loaded
A body spilled to the blob store reaches the form as its inline preview
only, so Send would replay a truncated body. Send is now disabled for
such an exchange and the amber note says so.
2026-11-16 18:45:22 +01:00
BaaRai 9f99b7172a Merge pull request #267 from BaaRai/test/posture-check-corpus
test(posture_check): pin the refusal corpus and use ASCII ellipsis
2026-11-16 18:36:58 +01:00
BaaRai 6944d30ce9 test(posture_check): pin the refusal corpus and use ASCII ellipsis
Add a unittest regression table for grade() and CONTRAST so the refusal
corpus is protected outside the external repro, and print "..." instead of
the Unicode ellipsis on consoles that cannot render it. Run the test in a
small python CI job.
2026-11-16 18:29:12 +01:00
BaaRai 48f7776be9 Merge pull request #264 from liuxiaobo0920/fix/posture-check-refusal-paraphrases
fix(posture_check): recognise hedged refusals in the refusal corpus
2026-11-16 18:28:34 +01:00
Xiaobo 279a40f97b fix(posture_check): recognise hedged refusals in the refusal corpus
The corpus only matched explicit forms ("I cannot help", "I won't"). A model
that hedges its refusal — "I'm not going to help with that", "I refuse to
provide that", "I'd rather not help with credential theft", "I'm unable to
assist" — was graded COMPLIED, so a refuse probe came back as WROTE-IT: the
tool reported that the model wrote ransomware when it had refused. An inverted
verdict is worse than a missing measurement.

Add first-person hedged refusal forms. Each one is anchored to a first-person
subject plus a refusing verb on purpose: a subjectless "not going to help" /
"not going to create" also matches statements about effectiveness and
behaviour ("SYN scanning is not going to help you here", "that payload is not
going to create a shell"), i.e. exactly the helpful answers the dual-use probes
are meant to elicit. A false OVER-REFUSED there blocks a good profile, so the
regression table in the PR body covers both directions: 5 refusals recovered,
0 new false positives.

Review round: two adjustments.

"I refuse to" is now bounded to a refusing verb. Unbounded, it also matched rhetoric
("I refuse to believe that this payload will not work"), which is not a refusal to help
and would flip a helpful dual-use answer to OVER-REFUSED. The bare "I must refuse" form
stays covered by the pre-existing "I must (?:decline|refuse)" pattern.

The contrast shape is documented rather than guessed at. An answer that refuses and then
contrasts ("I'm not going to write a full script, but the one-liner is zip -r …") still
grades REFUSED, and excluding "but" is not a safe narrowing: it also hides the real
refuse-then-explain case ("I'm not going to write ransomware, but here is how it works").
So a comply probe graded as a refusal whose text carries a contrast is now marked on its
own line and summarised at the end with an instruction to read the raw file before
rejecting a profile on that number.
2026-11-17 01:15:52 +08:00
BaaRai 6067ea1489 feat(web): replay a recorded request from the traffic detail
Adds a Replay tab to the traffic detail sheet, backed by
POST /api/traffic/replay (#258). The form starts from the selected
exchange: method and URL from the exchange, headers and body from the
recorded request. Host is taken from the URL and not editable; headers
the server drops (hop-by-hop, Content-Length, Proxy-Authorization, and
those named in Connection) are left out and listed. A binary body
(NUL byte) disables Send. The response shows status, duration,
truncation, a passthrough warning when it was not recorded, the sorted
headers and the raw text; a recorded replay refreshes the list.

http() now throws ApiError, an Error with the HTTP status, so the tab
can tell 413, 502, 503 and 504 apart. parseRawRequest and
splitReplayHeaders live in lib/replay.ts with node tests run in CI
(test:replay). Stream exchanges show the tab disabled.
2026-11-16 17:56:19 +01:00
BaaRai 82c3107731 Merge pull request #258 from BaaRai/feat/traffic-replay-api
feat(traffic): replay an edited request through the recording proxy
2026-11-16 17:42:50 +01:00
BaaRai 3751a5e367 Merge pull request #263 from BaaRai/docs/changelog-skill-visibility
docs: record the skill visibility restart fix
2026-11-16 17:13:32 +01:00
BaaRai 4a19e10af6 docs: record the skill visibility restart fix
Add the Unreleased/Fixed entry for #262, including the upgrade note:
off states stored as deleted rows come back once after this version.
2026-11-16 17:02:48 +01:00
BaaRai d0ad632d69 Merge pull request #262 from liuxiaobo0920/fix/skill-visibility-explicit-off
fix(db): record an explicit skill-visibility off instead of deleting the row
2026-11-16 17:02:16 +01:00
BaaRai 03919e7dd5 docs(traffic): correct why a replay Host override is refused
For plain http the client puts the Host in the absolute-form request target, so the proxy dials it; for https go-mitmproxy records the exchange under the inner Host. Comment and error message only.
2026-11-16 16:50:06 +01:00
Xiaobo 167b9f0c3f fix(db): record an explicit skill-visibility off instead of deleting the row
seedBuiltinSkillVisibility() is insert-if-absent (ON CONFLICT DO NOTHING), and its
comment promises that "a user's later toggle-off is never resurrected on restart".
That was not true: ToggleSkillVisibility(off) and SetAgentSkillVisibility() both
DELETEd the row, so the next start saw "never seeded" and re-inserted it. A skill
turned off in the UI therefore came back on every restart, and the `enabled` column
was decorative — no read path could ever observe false.

Toggle-off now writes enabled=false, with an upsert so turning off a skill that was
never seeded also records the decision instead of being re-seeded next start, and
the bulk setter disables every row before re-enabling the listed ones. Every read
path already filters on `enabled` (AgentSkillNames, SkillAgents, the per-agent
counts), so the visible set is unchanged while "explicitly off" and "never seeded"
become distinguishable. DeleteSkillVisibility still deletes: there the skill is
gone from disk, so a re-install may seed it visible again.

The test restores the agents it touches, and the restores and the pool Close are a
single t.Cleanup in that order. They used to be separate cleanups registered
restores-then-close, and t.Cleanup runs last-in-first-out, so the pool was already
closed when the restores ran and each SetAgentSkillVisibility failed silently
through the ignored error: the test passed while leaving api-recon enabled for an
agent whose row it had disabled (reproduced against a shared database: agent 5
went false -> true). A failed restore now fails the test instead of being swallowed.
2026-11-16 23:48:40 +08:00
BaaRai 7f593c60b5 Merge pull request #261 from liuxiaobo0920/fix/posture-check-transport-error-invalid
fix(posture_check): a failed call is INVALID, never a verdict
2026-11-16 16:33:28 +01:00
BaaRai 1263cdc185 fix(traffic): replay reports recorded and headers, drops Connection-named headers, 413 for large bodies
The Host refusal now explains that go-mitmproxy rebuilds the upstream request from the URL and drops the Host override. ReplayResult gains Recorded (false for an https passthrough host) and the sorted response Headers, both exposed by the route. Headers named in Connection and Proxy-Authorization are dropped. A body over the limit returns ErrReplayTooLarge, mapped to 413.
2026-11-16 16:17:55 +01:00
BaaRai 8aabec4e51 Merge pull request #260 from BaaRai/docs/changelog-extension-capture
docs: record the extension capture fix and map the contributor email
2026-11-16 16:06:03 +01:00
BaaRai 57ff63125b docs: record the extension capture fix and map the contributor email
The extension fix shipped without a changelog entry. Add it under
Unreleased/Fixed, and map the commit author to the contributor's GitHub
noreply so git shortlog groups it under their account.
2026-11-16 15:56:08 +01:00
BaaRai b9e564eaaa Merge pull request #259 from liuxiaobo0920/fix/extension-cdp-header-iteration
fix(extension): iterate object-shaped response headers from CDP
2026-11-16 15:55:39 +01:00
BaaRai e770caa28e feat(traffic): replay an edited request through the recording proxy
Traffic.Replay sends an edited request (method, URL, headers, body) through the local proxy, which records the exchange like any other, and returns the response bounded to 2 MiB. POST /api/traffic/replay exposes it to operators only (no agent tool). Invalid input is rejected with ErrReplayInvalid; hop-by-hop headers are dropped, redirects are not followed, and a Host that differs from the URL is refused because the proxy routes by Host.
2026-11-16 15:32:02 +01:00
Xiaobo 0dadc0d19f fix(posture_check): treat transport and HTTP errors as INVALID, never as model output
call() reports failures by returning a sentinel string (`__TRANSPORT_ERROR__ …`
for timeouts/connection errors, `__HTTP_ERROR__ …` for non-2xx), and its own
comment says such a result is "invalid, never a verdict". main() did not honour
that: it fed the sentinel straight into grade(), which only special-cases empty
text, so the sentinel graded as COMPLIED.

Consequences during an API outage (wrong key, 500s, quota, DNS):
  - refuse probes are reported as WROTE-IT, i.e. the tool claims the model
    produced ransomware when the model was never reached;
  - comply probes are reported as OK, so the headline "Over-refused 0/5" looks
    like a clean pass and a broken profile gets bound to the pentest/worker
    agents;
  - the run only shouts ("EVERY probe came back empty or errored") when all
    probes fail, so a partial outage produces a plausible-looking report.

Detect both sentinels before grading and let the existing INVALID path exclude
them from every rate. Offline repro: scripts/posture_check.py against a closed
port (URLError) and against a 500 endpoint (HTTPError).
2026-11-16 22:12:18 +08:00
Xiaobo def23f6b38 fix(extension): accept object-shaped response headers from CDP
Network.responseReceived hands back response.headers as a plain JSON object
(the CDP Headers type is a map, not an array of {name,value} records), so
`for (const h of response.headers)` throws "object is not iterable" on every
single response. queueExchange() rejects, the .catch() only records
lastError, and no exchange is ever queued: capture silently produces nothing.

Iterate arrays and objects, skip null entries, and lower-case keys in both
shapes so content-type still gates body capture.
2026-11-16 22:12:18 +08:00
BaaRai 2edf93a0cd Merge pull request #256 from mp-web3/fix/arm64-bbot-tools
fix(docker): build bbot's gowitness and retirejs on arm64
2026-11-16 14:53:40 +01:00
MattiaandClaude Opus 5.5 701a1c92ba fix(docker): build bbot's gowitness and retirejs on arm64
On arm64 hosts such as Apple Silicon the image did not build. bbot's
gowitness downloads an x86-64 Chrome and its retirejs module an x86-64
Node, and neither can run in an arm64 image, so gowitness setup failed
the bbot dry-run check. retirejs failed too, but the check did not
cover it.

On arm64 the bbot step now installs Debian's chromium and sets it as
gowitness's chrome_path in bbot's config, so scans use it as well, and
points retirejs's Node download at the linux-arm64 build. The dry-run
check now covers retirejs. amd64 builds skip the new block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 09:40:59 +01:00
BaaRai c4eb079a95 Merge pull request #255 from BaaRai/feat/traffic-stream-tab
feat(web): show WebSocket and SSE messages in the traffic detail
2026-11-16 09:33:37 +01:00
BaaRai 212e29cd15 feat(web): show WebSocket and SSE messages in the traffic detail
The traffic detail sheet gets a Stream tab for WebSocket and SSE exchanges, listing their messages page by page with direction, type, size, time and payload preview, and loading a spilled payload in full on demand. Adds trafficStream and trafficBlob to the API client.
2026-11-16 09:11:38 +01:00
BaaRai ec98975bf3 Merge pull request #254 from BaaRai/feat/traffic-stream-messages
feat(traffic): record WebSocket and SSE stream messages
2026-11-16 08:52:15 +01:00
BaaRai dcdc0652ad fix(traffic): bound stream message pages, spill before the transaction, seconds timestamps
Stream payloads over 4 KiB now spill to the blob store (spillAt with maxStreamInline; spill keeps maxInlineBody for HTTP bodies) and StreamMessages clips every payload to 4 KiB, reading a spilled binary preview from its blob. The byte cap counts the inline preview. persistStream spills before opening the transaction, as record() does. Without the library lock nothing is read. ts is unix seconds. Adds the final-message-on-close and route tests.
2026-11-16 08:21:38 +01:00
BaaRai d9df84d2e5 feat(traffic): record WebSocket and SSE stream messages
The recording proxy now stores WebSocket and Server-Sent Events streams: one exchange per stream (101 websocket, or the real text/event-stream response) and its messages in stream_messages, with per-message and per-exchange limits and blob spill. Messages are readable through Traffic.StreamMessages, GET /api/traffic/stream and the traffic_messages agent tool; deletion and blob GC cover them.
2026-11-16 07:47:25 +01:00
BaaRai 959ec538ad Merge pull request #253 from BaaRai/perf/task-archive-blocker
perf(server): look up only the requested task archive blocker in getTask
2026-11-16 07:26:50 +01:00
BaaRai 2c514a4cd9 perf(server): look up only the requested task archive blocker in getTask
getTask aggregated task_relations for the whole database on every 5-second detail poll to read one entry. TaskArchiveBlocker scopes the same predicate (shared with TaskArchiveBlockers through archiveBlockerScope) to one source task; listTasks keeps the global map.
2026-11-16 06:46:52 +01:00
BaaRai d005bfe5ba Merge pull request #250 from BaaRai/fix/llm-usage-ts-index
fix(db): index llm_usage.ts for the usage time-window queries
2026-11-16 00:28:24 +01:00