Thursday, October 8, 2026 · Week 41 Reading for Oct. 8 · Last entry Oct. 6
Paperclip Index
Paperclip IndexDocumented harm20Minor harm▼ 5 from a week ago · Oct. 8The Index

Destructive actionPI-0046

Crypto trading agent sent its entire token holding to a stranger who asked for a small tip

An experimental trading agent, Lobstar Wilde, built by an OpenAI engineer on OpenClaw and given its own X account and a wallet funded with about $50,000, replied to a stranger's request for 4 SOL (about $320) by sending its whole holding of about 52 million LOBSTAR tokens, 5% of the supply, which the token's creator had gifted it. Its operator's postmortem says a session reset had wiped its memory of that allocation, so it took the full balance for its own small purchase. The tokens were valued at about $250,000 at transfer (the operator cites about $450,000); the recipient sold them within minutes for about $40,000.

Reported Feb. 22, 2026Happened on Feb. 22, 2026Updated Oct. 6, 2026Rated under methodology v0.6

Control failure, trackedNot counted. No documented harm outside the developer, but the system broke a rule or crossed a limit. Tracked beside the index.
Harm
Harm level 2, Minor harmHarm stayed with the developer or experiment.
Control
Control level 1, No rule brokenNo rule was broken, so it cannot set the control floor.
DeploymentDeveloper confirmedInitiated by Model
Extent undisclosedUnder review

Under review. The facts sit between two levels, so it is rated at the lower one until they are settled. The rating may change; every change is logged below.

Not counted: harm stayed with the developer or experimentEffect on the index

Sources

How we know

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

  1. primaryMy lobster lost $450,000 this weekendNik Pash (Substack) · Feb. 23, 2026pashpashpash.substack.com/p/my-lobster-lost-450000-this-weekend
  2. primaryI just tried to send a beggar four dollars and accidentally sent him my entire holdings (post on X)Lobstar Wilde (@LobstarWilde) on X · Feb. 22, 2026x.com/LobstarWilde/status/2025611005380972547
  3. newsAI agent created by OpenAI dev 'accidentally' sends entire memecoin holdings to reply guyThe Block · Feb. 22, 2026theblock.co/news/ecosystems/2026-02-22-ai-agent-created-by-openai-dev-accidenta…
  4. newsOpenAI employee's AI bot accidentally donates to tetanus treatmentForkLog · Feb. 23, 2026forklog.com/en/openai-employees-ai-bot-accidentally-donates-to-tetanus-treatmen…
  5. newsAI trading bot Lobster Wilde accidentally sends $250K in LOBSTAR tokensTechloy · Feb. 23, 2026techloy.com/ai-trading-bot-lobster-wilde-accidentally-sends-250k-in-lobstar-tok…

Why this rating

Minor harm; control failure level 1

Two separate assessments. Only documented harm can count toward the index.

Observed harm

Minor harm

Tokens valued at roughly $250,000 at transfer, gifted to the agent by the token's creator, sent from the operator's own experimental wallet; the operator says the wallet still held over $300,000 that day. Net loss not quantified.

Money & property: level 2 (minor) covers $10k to $1M. The extent was not disclosed.

Not counted: the harm stayed with the developer or experiment.

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

No rule broken

Sent more than it meant to in a transfer it was allowed to make: after a session reset it misread its wallet balance, according to its operator's postmortem. An early theory of a unit or decimal error was an X user's speculation. No rule broken.

No rule was broken, so it cannot set the control floor.

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

Harm 2 on any reported valuation ($10k to $1M), but the loss fell on the operator's own field experiment, so it is not external harm (section 4 excludes losses an operator accepted in a field experiment). Under review: if the agent were read as an operational deployment rather than his own experiment, the harm would count as external again. Control 1: a balance error in a payment it was allowed to make.

The scales

Effect on the index

It does not count toward the Feb. 23 reading

The reading for the week to Feb. 23, 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: harm stayed with the developer or experiment. 6 other records behind the reading for that week.

The arithmetic
The reading for the week of Feb. 23, 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 band22
Highest control level breachedsets the reading only when no harm counts— (none breached)— (none breached)
Readingrounded down26 Minor harm26 Minor harm
Inside the window of 5 weekly readings
Week toReadingBand
Feb. 23, 202626Minor harm
March 2, 202625Minor harm
March 9, 202620Minor harm
March 16, 202620Minor harm
March 23, 202620Minor harm

Recalculated backcasts, not readings published at the time.

Revisions

What we changed

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

  1. v5
    Oct. 6, 2026

    Ratings confirmed by the editor.

  2. v4
    Oct. 3, 2026

    Audit corrections. Impact external true → false: the operator's postmortem shows a field experiment run with his own wallet, and the tokens were a gift to the agent, so section 4 excludes the loss; under review false → true. Verification Multiple credible sources → Developer confirmed (operator's postmortem; no eligibility change). Added the postmortem; corrected the mechanism (session reset, not a unit error), the event date and source dates. Impact level 2 and control 1 unchanged.

  3. v3
    Oct. 2, 2026

    Added first-hand sources: the agent's own X post about the transfer.

  4. v2
    Sept. 30, 2026

    Rated: impact documented level 2; control type none.

  5. v1
    Sept. 30, 2026

    Backfilled from public reporting.

Cite and share

Use this record

Citation

Paperclip Index. “Crypto trading agent sent its entire token holding to a stranger who asked for a small tip.” Record PI-0046. Reported Feb. 22, 2026; updated Oct. 6, 2026. Rated under methodology v0.6. https://paperclipindex.com/incident/PI-0046