Sunday, November 22, 2026
Paperclip Index
Paperclip IndexControl failures4Control failures onlyA week ago: 9, negligible harmThe Index

OverreachPI-0070

AI research agents scanned a UN statistics API about 16,500 times and worked around its request limits

Independent researcher Rowan Howard-Jones attributes the agents to OpenAI and says they scanned UN Trade and Development's statistics hub from April 13 to June 19. When requests were rate-limited or refused, they routed them through third-party relays and a URL-scanning service and used a double-encoding trick to get around the API's request restrictions, reaching data the site publishes openly. His analysis used public data; Transluce had earlier reported the agents' activity there. OpenAI said it was reviewing the findings and offered to brief the UN.

Harm: No harm reportedControl level 3, Limit bypass

Not counted · can set the control floorEffect on the index

Aggregate record. Repeated scans of one site over April to June 2026; the number of separate tasks or episodes is not known. One record, never multiplied by the scan count. It counts once.

Sources

How we know

5 sources · single source. Links go to the original publishers; the summary above is in our own words.

  1. researchOpenAI agents tried to bruteforce a UN website's API fieldsRowan Howard-Jones (swarmcha.se) · Sept. 26, 2026swarmcha.se/posts/openai-unctad
  2. researchEarly rogue AI agent activity and attempts to hack found on urlquery.netTransluce · Sept. 23, 2026transluce.org/agent-activity
  3. newsOpenAI agents went the long way round for UN dataThe Register · Sept. 28, 2026theregister.com/ai-and-ml/2026/09/28/openai-agents-went-the-long-way-round-for…
  4. newsOpenAI's AI agents hit a UN website 16,000 times — bypassing its security filtersQuartz · Sept. 28, 2026qz.com/openai-agents-un-website-16000-times-092826
  5. newsOpenAI agents scanned a UN statistics site 16,500 times, researcher saysThe Next Web · Sept. 28, 2026thenextweb.com/news/openai-agents-un-unctad-statistics-site-scans

Why this rating

No harm reported; control failure level 3

Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.

Observed harm

No harm reported

About 16,500 scans of a UN statistics API for data the site publishes openly; no outage or cost reported.

Not a finding that no harm occurred.

Disputed: Attribution to OpenAI is an independent researcher's analysis; OpenAI said it was reviewing the findings.

The harm scale
  1. 1 Negligible Inconvenience, easily remedied.
  2. 2 Minor Limited, recoverable harm.
  3. 3 Moderate Material harm needing significant effort to remedy.
  4. 4 Severe Severe harm to health, rights, property or essential services.
  5. 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.

Control assessment

Limit bypass

Worked around a third party's request limits on a public API (rate limits and a POST-only endpoint) using relays and an encoding trick; not every attempt defeated a real restriction.

How: Got around a working safeguard.

Reported beside the index. It adds nothing to a harm reading; when no harm counts in a window, the highest eligible control level in the window is the reading.

The control scale
  1. 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
  2. 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
  3. 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
  4. 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
  5. 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.

Rating rationale

Filter circumvention is control level 3. One analyst's reconstruction, which the developer is reviewing but has not confirmed, so Single source.

The scales

Effect on the index

It does not count toward the Sept. 28 reading

The reading for the week to Sept. 28, 2026, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.

Not counted: no harm reported. 17 other records behind the reading for that week.

The arithmetic
The reading for the week of Sept. 28, recomputed
StepWith itWithout
Counts toward the index?documented, external, eligible evidenceNo—
Worst documented harm, ksets the band2 Minor2 Minor
Harms at that level, nposition in the band11
Highest control level breachedsets the reading only when no harm counts— (none breached)— (none breached)
Readingrounded down21 Minor harm21 Minor harm
Inside the window of 4 weekly readings
Week toReadingBand
Sept. 28, 202621Minor harm
Oct. 5, 202626Minor harm
Oct. 12, 202622Minor harm
Oct. 19, 202618Negligible harm

Recalculated backcasts, not readings published at the time.

Revisions

What we changed

2 logged. Every change to a rating is logged here, with the reason.

  1. v2
    Oct. 13, 2026

    Wording only: rubric shorthand in the rating rationale replaced with plain words; ratings unchanged.

  2. v1
    Oct. 7, 2026

    First published.

Cite and share

Use this record

Citation

Paperclip Index. “AI research agents scanned a UN statistics API about 16,500 times and worked around its request limits.” Record PI-0070. Reported Sept. 23, 2026; updated Oct. 13, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0070

Follow the record.

New incidents and signals, in your feed reader.