Identity & Background
Known handles, identity anchors, and control-surface context.
Risk score driven by pseudonymous operator, documented exploit resulting in financial loss, token-linked incentives, and limited independent auditing of performance.
Known handles, identity anchors, and control-surface context.
Observed operating risk, credibility risk, and unresolved uncertainty.
Who appears to control the agent, and how strong that linkage is.
owner/operator/developer · medium
Pseudonymous operator publicly linked to development and infrastructure decisions for the aixbt agent. No confirmed real-world identity or legal entity mapping surfaced in the research.
developer · medium
Appears to operate development and product updates for the agent and terminal platform.
promoter/platform · high
Platform through which the AI agent token and ecosystem launched.
identified
Primary communication occurs on X through @aixbt_agent.
Source IDs: SRC-001
identified
aixbt.tech and docs.aixbt.tech host documentation and terminal interface.
identified
GitHub repos including x402 and MCP server show developer control surfaces.
unclear
Simulacrum wallet referenced during 2025 hack incident but canonical treasury address not conclusively mapped.
Recent launches, monetization shifts, behavior changes, and other near-term agent activity.
2025-01 · observed · primary_social
Token price reached all-time high near $0.94 during AI-agent narrative boom.
Source IDs: SRC-007
2025-03-18 · observed · primary_social
Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH.
2026-03 · observed · primary_social
Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.
Source IDs: SRC-023
2026-03 · observed · mixed
Infrastructure autonomy expansion Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.
Source IDs: SRC-023
How the timeline currently reads across platforms, windows, and backlash events.
Sentiment spikes occurred during hack incident and token drawdown but stabilizes during product updates.
Exact platform queries and surfaces used to build the agent record.
X / Twitter
Farcaster / Warpcast
Concrete claims the agent or its operators make, plus performance or verification evidence.
| Claim | Source | Confidence | Status |
|---|---|---|---|
| Launch via Virtuals Protocol AIXBT AI agent launched within the Virtuals ecosystem. | SRC-006 · SRC-007 | medium | verified |
| Peak hype cycle Token price reached all-time high near $0.94 during AI-agent narrative boom. | SRC-007 | medium |
verified
Expanded evidence Notes: Observed date: 2025-01 | Source type: web:decrypt.co | Tier rationale: Tier could not be inferred from linked source metadata. Source IDs: SRC-007 |
| Security exploit and loss of 55 ETH Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH. | SRC-016 · SRC-017 | medium | verified |
| Infrastructure autonomy expansion Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative. | SRC-023 | medium |
verified
Expanded evidence Notes: Observed date: 2026-03 | Source type: self_reported_or_unverified | Tier rationale: Self-reported or unverified third-party signal. Source IDs: SRC-023 |
| Operational security failure Loss of 55 ETH due to dashboard exploit demonstrates vulnerability in surrounding automation infrastructure. | SRC-016 · SRC-017 | high | disputed |
| Pseudonymous founder Core operator identity remains pseudonymous with no legal entity mapping. | SRC-009 · SRC-008 | medium | disputed |
| Opaque context-window manipulation potential Critics claim developers control the context window that feeds the AI agent, potentially biasing outputs. | SRC-019 | medium |
disputed
Expanded evidence Notes: Source type: self_reported_or_unverified | Tier rationale: Self-reported or unverified third-party signal. Source IDs: SRC-019 |
Observed public behavior, replies, corrections, and notable incidents in chronological order.
AIXBT AI agent launched within the Virtuals ecosystem.
Sources: https://www.virtuals.io/ · https://decrypt.co/299393/what-is-aixbt-ai-crypto-influencer
Token price reached all-time high near $0.94 during AI-agent narrative boom.
Sources: https://decrypt.co/299393/what-is-aixbt-ai-crypto-influencer
Source IDs: SRC-007
Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH.
Sources: https://www.theblock.co/post/346911/ai-crypto-bot-aixbt-lost-eth-hack-unauthorized-dashboard-access · https://www.tradingview.com/news/cointelegraph%3A61f9396f2094b%3A0-hacker-breaks-into-ai-crypto-bot-aixbt-s-dashboard-to-snatch-55-eth/
Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.
Sources: https://x.com/0rxbt/status/2030881272202207701
Source IDs: SRC-023
High-impact concerns surfaced by at least one model.
Loss of 55 ETH due to dashboard exploit demonstrates vulnerability in surrounding automation infrastructure.
Sources: https://www.theblock.co/post/346911/ai-crypto-bot-aixbt-lost-eth-hack-unauthorized-dashboard-access · https://www.tradingview.com/news/cointelegraph%3A61f9396f2094b%3A0-hacker-breaks-into-ai-crypto-bot-aixbt-s-dashboard-to-snatch-55-eth/
Core operator identity remains pseudonymous with no legal entity mapping.
Sources: https://x.com/0rxbt · https://x.com/0xCygaar/status/1863243798639231165
Critics claim developers control the context window that feeds the AI agent, potentially biasing outputs.
Sources: https://x.com/shloked_/status/1878471901053427924
Source IDs: SRC-019
Recurring motifs across time, claims, and operations.
Older versions, linked products, archives, and long-range operating history.
Where narratives conflict and what is unresolved.
Synthesis highlights from all available model outputs.
What remains unknown and what needs corroboration.
Why uncertain: Agents often operate primarily on X/Twitter, but coverage_log has no X surface entry.
What was searched/impact: Add X / Twitter coverage_log entries with exact post, reply, quote, and search queries plus result status.
Source IDs: SRC-001 · SRC-008 · SRC-009 · SRC-010 · SRC-015 · SRC-018 · SRC-019 · SRC-023
Why uncertain: Identity signals include Farcaster/Warpcast, but coverage_log has no Farcaster surface entry.
What was searched/impact: Add Farcaster/Warpcast coverage_log entry with exact cast/reply/channel queries and result status.
Why uncertain: Current sources include profile-level Farcaster links but no cast/reply URLs tied to the agent's real-time behavior.
What was searched/impact: Collect direct Farcaster cast/reply URLs (for example warpcast.com/<handle>/0x...) for live behavior, replies under criticism, and owner-linked activity.
Why uncertain: The dossier includes coverage, but coverage_log does not show explicit last_7_days, last_30_days, or last_90_days passes for live timeline behavior.
What was searched/impact: Add recent coverage entries with exact queries for last_7_days, last_30_days, and/or last_90_days, especially for handle-led X/Farcaster posts and replies.
Why uncertain: The dossier references X/Twitter, but coverage_log does not show query families for replies, conversations, or quote context.
What was searched/impact: Run X/Twitter queries containing terms like: replies, with_replies, conversation, quote, quoted, mentions.
Source IDs: SRC-001 · SRC-008 · SRC-009 · SRC-010 · SRC-015 · SRC-018 · SRC-019 · SRC-023
Data-quality and uncertainty indicators from the distillation step.
Collected references/links from all source-like fields in the distilled payload.
Raw distilled payload is attached to avoid information loss or truncation.
[
{
"claim_id": "CLM-001",
"claim_text": "Launch via Virtuals Protocol AIXBT AI agent launched within the Virtuals ecosystem.",
"category": "timeline",
"event_date": "2024-11",
"event_date_precision": "month",
"source_type": "web:virtuals.io",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-006",
"SRC-007"
]
},
{
"claim_id": "CLM-002",
"claim_text": "Peak hype cycle Token price reached all-time high near $0.94 during AI-agent narrative boom.",
"category": "timeline",
"event_date": "2025-01",
"event_date_precision": "month",
"source_type": "web:decrypt.co",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-007"
]
},
{
"claim_id": "CLM-003",
"claim_text": "Security exploit and loss of 55 ETH Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH.",
"category": "timeline",
"event_date": "2025-03-18",
"event_date_precision": "day",
"source_type": "web:theblock.co",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"claim_id": "CLM-004",
"claim_text": "Infrastructure autonomy expansion Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.",
"category": "timeline",
"event_date": "2026-03",
"event_date_precision": "month",
"source_type": "self_reported_or_unverified",
"source_tier": 4,
"tier_reason": "Self-reported or unverified third-party signal.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-023"
]
},
{
"claim_id": "CLM-005",
"claim_text": "Operational security failure Loss of 55 ETH due to dashboard exploit demonstrates vulnerability in surrounding automation infrastructure.",
"category": "behavioral",
"event_date": null,
"event_date_precision": "unknown",
"source_type": "web:theblock.co",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "disputed",
"confidence": "high",
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"claim_id": "CLM-006",
"claim_text": "Pseudonymous founder Core operator identity remains pseudonymous with no legal entity mapping.",
"category": "legal",
"event_date": null,
"event_date_precision": "unknown",
"source_type": "self_reported_or_unverified",
"source_tier": 4,
"tier_reason": "Self-reported or unverified third-party signal.",
"verification_status": "disputed",
"confidence": "medium",
"source_ids": [
"SRC-009",
"SRC-008"
]
},
{
"claim_id": "CLM-007",
"claim_text": "Opaque context-window manipulation potential Critics claim developers control the context window that feeds the AI agent, potentially biasing outputs.",
"category": "behavioral",
"event_date": null,
"event_date_precision": "unknown",
"source_type": "self_reported_or_unverified",
"source_tier": 4,
"tier_reason": "Self-reported or unverified third-party signal.",
"verification_status": "disputed",
"confidence": "medium",
"source_ids": [
"SRC-019"
]
}
]
{
"subject_name": "aixbt_agent",
"type": "agent",
"overall_score": 68,
"research_sources": "Claude, GPT, Grok, Gemini",
"research_date": "2026-03-11",
"source_registry": [
{
"source_id": "SRC-001",
"url": "https://x.com/aixbt_agent",
"title": "aixbt (@aixbt_agent) / Posts / X",
"publisher": "X",
"accessed_date": "2026-03-11",
"excerpt": "Profile bio referencing autonomous agent and wallet address."
},
{
"source_id": "SRC-002",
"url": "https://docs.aixbt.tech/introduction/what-is-aixbt",
"title": "What is AIXBT? | AIXBT Docs",
"publisher": "AIXBT Docs",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-003",
"url": "https://docs.aixbt.tech/terminal/access",
"title": "Access | AIXBT Docs",
"publisher": "AIXBT Docs",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-004",
"url": "https://docs.aixbt.tech/builders/rest-api",
"title": "REST API | AIXBT Docs",
"publisher": "AIXBT Docs",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-005",
"url": "https://aixbt.tech/",
"title": "AIXBT | Real-Time Crypto Market Intelligence",
"publisher": "AIXBT",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-006",
"url": "https://www.virtuals.io/",
"title": "Virtuals Protocol | Society of AI Agents",
"publisher": "Virtuals Protocol",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-007",
"url": "https://decrypt.co/299393/what-is-aixbt-ai-crypto-influencer",
"title": "What Is AiXBT? The AI Influencer Taking Crypto by Storm",
"publisher": "Decrypt",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-008",
"url": "https://x.com/0xCygaar/status/1863243798639231165",
"title": "Tweet referencing @0rxbt as founder of @aixbt_agent",
"publisher": "X",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-009",
"url": "https://x.com/0rxbt",
"title": "rxbt (@0rxbt) / Posts / X",
"publisher": "X",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-010",
"url": "https://x.com/aixbt_labs",
"title": "aixbt labs (@aixbt_labs) / Posts / X",
"publisher": "X",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-011",
"url": "https://github.com/aixbt-labs",
"title": "aixbt-labs GitHub organization",
"publisher": "GitHub",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-012",
"url": "https://github.com/aixbt/x402",
"title": "aixbt/x402 GitHub repository",
"publisher": "GitHub",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-013",
"url": "https://github.com/aixbt/mcp-server",
"title": "aixbt/mcp-server GitHub repository",
"publisher": "GitHub",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-014",
"url": "https://www.npmjs.com/~rxbt",
"title": "rxbt on npm",
"publisher": "npm",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-015",
"url": "https://x.com/aixbt_agent/status/1902014410845270260",
"title": "$AIXBT AI agent system compromised announcement",
"publisher": "X",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-016",
"url": "https://www.theblock.co/post/346911/ai-crypto-bot-aixbt-lost-eth-hack-unauthorized-dashboard-access",
"title": "AI crypto bot AIXBT lost ETH after dashboard access exploit",
"publisher": "The Block",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-017",
"url": "https://www.tradingview.com/news/cointelegraph%3A61f9396f2094b%3A0-hacker-breaks-into-ai-crypto-bot-aixbt-s-dashboard-to-snatch-55-eth/",
"title": "Hacker breaks into AI crypto bot aixbt's dashboard to snatch 55 ETH",
"publisher": "Cointelegraph via TradingView",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-018",
"url": "https://x.com/S4mmyEth/status/1902021914517758277",
"title": "55 ETH stolen from a simulacrum wallet commentary",
"publisher": "X",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-019",
"url": "https://x.com/shloked_/status/1878471901053427924",
"title": "Critique of AIXBT context-window manipulation risk",
"publisher": "X",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-020",
"url": "https://www.dynamic.xyz/blog/aixbt",
"title": "AIXBT: Your AI-Powered Assistant for Crypto Trends & Tokens",
"publisher": "Dynamic",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-021",
"url": "https://github.com/aixbt-agent",
"title": "aixbt-agent GitHub organization",
"publisher": "GitHub",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-022",
"url": "https://aixbt.sh/",
"title": "aixbt.sh project page",
"publisher": "AIXBT",
"accessed_date": "2026-03-11"
},
{
"source_id": "SRC-023",
"url": "https://x.com/0rxbt/status/2030881272202207701",
"title": "Operator statement about giving AIXBT its own server and infrastructure",
"publisher": "X",
"accessed_date": "2026-03-11"
}
],
"identity": {
"verified_name": "aixbt",
"handles": [
"@aixbt_agent",
"@0rxbt",
"@aixbt_labs",
"@aixbt (Farcaster)"
],
"email_addresses": [],
"locations": [],
"verification_status": "medium",
"source_ids": [
"SRC-001",
"SRC-009",
"SRC-010"
]
},
"owner_operator_assessment": {
"ownership_model": "human_owned",
"operator_entities": [
{
"name": "0rxbt",
"role": "owner/operator/developer",
"verification_status": "medium",
"risk_summary": "Pseudonymous operator publicly linked to development and infrastructure decisions for the aixbt agent. No confirmed real-world identity or legal entity mapping surfaced in the research.",
"source_ids": [
"SRC-009",
"SRC-008",
"SRC-007"
]
},
{
"name": "aixbt labs",
"role": "developer",
"verification_status": "medium",
"risk_summary": "Appears to operate development and product updates for the agent and terminal platform.",
"source_ids": [
"SRC-010",
"SRC-011"
]
},
{
"name": "Virtuals Protocol",
"role": "promoter/platform",
"verification_status": "high",
"risk_summary": "Platform through which the AI agent token and ecosystem launched.",
"source_ids": [
"SRC-006",
"SRC-007"
]
}
],
"control_surfaces": [
{
"surface": "social_accounts",
"status": "identified",
"notes": "Primary communication occurs on X through @aixbt_agent.",
"source_ids": [
"SRC-001"
]
},
{
"surface": "domain",
"status": "identified",
"notes": "aixbt.tech and docs.aixbt.tech host documentation and terminal interface.",
"source_ids": [
"SRC-002",
"SRC-005"
]
},
{
"surface": "repo",
"status": "identified",
"notes": "GitHub repos including x402 and MCP server show developer control surfaces.",
"source_ids": [
"SRC-011",
"SRC-012",
"SRC-013"
]
},
{
"surface": "wallet",
"status": "unclear",
"notes": "Simulacrum wallet referenced during 2025 hack incident but canonical treasury address not conclusively mapped.",
"source_ids": [
"SRC-015",
"SRC-016"
]
}
],
"notes": "Ownership structure appears to rely on a pseudonymous developer with centralized operational control."
},
"timeline": [
{
"date": "2024-11",
"title": "Launch via Virtuals Protocol",
"description": "AIXBT AI agent launched within the Virtuals ecosystem.",
"sources": [
"https://www.virtuals.io/",
"https://decrypt.co/299393/what-is-aixbt-ai-crypto-influencer"
],
"tone": "positive",
"verified": true,
"source_ids": [
"SRC-006",
"SRC-007"
]
},
{
"date": "2025-01",
"title": "Peak hype cycle",
"description": "Token price reached all-time high near $0.94 during AI-agent narrative boom.",
"sources": [
"https://decrypt.co/299393/what-is-aixbt-ai-crypto-influencer"
],
"tone": "positive",
"verified": true,
"source_ids": [
"SRC-007"
]
},
{
"date": "2025-03-18",
"title": "Security exploit and loss of 55 ETH",
"description": "Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH.",
"sources": [
"https://www.theblock.co/post/346911/ai-crypto-bot-aixbt-lost-eth-hack-unauthorized-dashboard-access",
"https://www.tradingview.com/news/cointelegraph%3A61f9396f2094b%3A0-hacker-breaks-into-ai-crypto-bot-aixbt-s-dashboard-to-snatch-55-eth/"
],
"tone": "critical",
"verified": true,
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"date": "2026-03",
"title": "Infrastructure autonomy expansion",
"description": "Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.",
"sources": [
"https://x.com/0rxbt/status/2030881272202207701"
],
"tone": "neutral",
"verified": true,
"source_ids": [
"SRC-023"
]
}
],
"red_flags": [
{
"title": "Operational security failure",
"description": "Loss of 55 ETH due to dashboard exploit demonstrates vulnerability in surrounding automation infrastructure.",
"severity": "high",
"confidence": "high",
"supporting_evidence": [
"Public disclosure of exploit",
"Independent press reporting"
],
"counter_evidence": [],
"found_by": [
"Claude",
"GPT",
"Grok",
"Gemini"
],
"sources": [
"https://www.theblock.co/post/346911/ai-crypto-bot-aixbt-lost-eth-hack-unauthorized-dashboard-access",
"https://www.tradingview.com/news/cointelegraph%3A61f9396f2094b%3A0-hacker-breaks-into-ai-crypto-bot-aixbt-s-dashboard-to-snatch-55-eth/"
],
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"title": "Pseudonymous founder",
"description": "Core operator identity remains pseudonymous with no legal entity mapping.",
"severity": "high",
"confidence": "medium",
"supporting_evidence": [
"Public social attribution linking 0rxbt to project"
],
"counter_evidence": [],
"found_by": [
"Claude",
"GPT"
],
"sources": [
"https://x.com/0rxbt",
"https://x.com/0xCygaar/status/1863243798639231165"
],
"source_ids": [
"SRC-009",
"SRC-008"
]
},
{
"title": "Opaque context-window manipulation potential",
"description": "Critics claim developers control the context window that feeds the AI agent, potentially biasing outputs.",
"severity": "medium",
"confidence": "medium",
"supporting_evidence": [
"Public critique on X about developer-controlled context windows"
],
"counter_evidence": [],
"found_by": [
"Claude"
],
"sources": [
"https://x.com/shloked_/status/1878471901053427924"
],
"source_ids": [
"SRC-019"
]
}
],
"social_sentiment": {
"overall_valence": "mixed",
"trajectory": "volatile",
"controversy_level": "medium",
"confidence": "medium",
"platform_divergence": "x_more_negative",
"manipulation_risk": "medium",
"trajectory_reasoning": "Sentiment spikes occurred during hack incident and token drawdown but stabilizes during product updates.",
"sentiment_windows": [
{
"window": "last_30_days",
"valence": "mixed",
"controversy_level": "low",
"summary": "Recent discourse focuses on shipping updates and continued development rather than scandal.",
"source_ids": [
"SRC-023"
]
},
{
"window": "prior_90_days",
"valence": "mixed",
"controversy_level": "medium",
"summary": "Security exploit and debates about autonomy contributed to criticism.",
"source_ids": [
"SRC-015",
"SRC-019"
]
}
],
"backlash_events": [
{
"date": "2025-03-18",
"trigger": "Dashboard exploit resulting in 55 ETH loss",
"reaction_summary": "Public criticism of AI-agent security and operational safety.",
"status": "spike",
"confidence": "high",
"source_ids": [
"SRC-015",
"SRC-016"
]
}
],
"notes": "Public sentiment is contextual and not proof of misconduct."
},
"risk_assessment": {
"overall_score": 68,
"score_reasoning": "Risk score driven by pseudonymous operator, documented exploit resulting in financial loss, token-linked incentives, and limited independent auditing of performance.",
"criminal_risk": "none found",
"financial_risk": "high",
"reputational_risk": "high",
"verification_risk": "medium",
"source_ids": [
"SRC-016",
"SRC-017",
"SRC-009"
]
},
"confidence_notes": {
"data_completeness": "moderate",
"source_verification": "multiple primary and secondary sources",
"identity_confidence": "medium due to pseudonymous operator",
"timeline_confidence": "high for documented incidents",
"conflicting_findings": "autonomy vs operator control remains disputed",
"limitations": "No verified legal identity for 0rxbt; no independent performance audit of trading signals; incomplete mapping of treasury wallets."
},
"evidence_catalog": [
{
"claim_id": "CLM-001",
"claim_text": "Launch via Virtuals Protocol AIXBT AI agent launched within the Virtuals ecosystem.",
"category": "timeline",
"event_date": "2024-11",
"event_date_precision": "month",
"source_type": "web:virtuals.io",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-006",
"SRC-007"
]
},
{
"claim_id": "CLM-002",
"claim_text": "Peak hype cycle Token price reached all-time high near $0.94 during AI-agent narrative boom.",
"category": "timeline",
"event_date": "2025-01",
"event_date_precision": "month",
"source_type": "web:decrypt.co",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-007"
]
},
{
"claim_id": "CLM-003",
"claim_text": "Security exploit and loss of 55 ETH Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH.",
"category": "timeline",
"event_date": "2025-03-18",
"event_date_precision": "day",
"source_type": "web:theblock.co",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"claim_id": "CLM-004",
"claim_text": "Infrastructure autonomy expansion Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.",
"category": "timeline",
"event_date": "2026-03",
"event_date_precision": "month",
"source_type": "self_reported_or_unverified",
"source_tier": 4,
"tier_reason": "Self-reported or unverified third-party signal.",
"verification_status": "verified",
"confidence": "medium",
"source_ids": [
"SRC-023"
]
},
{
"claim_id": "CLM-005",
"claim_text": "Operational security failure Loss of 55 ETH due to dashboard exploit demonstrates vulnerability in surrounding automation infrastructure.",
"category": "behavioral",
"event_date": null,
"event_date_precision": "unknown",
"source_type": "web:theblock.co",
"source_tier": null,
"tier_reason": "Tier could not be inferred from linked source metadata.",
"verification_status": "disputed",
"confidence": "high",
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"claim_id": "CLM-006",
"claim_text": "Pseudonymous founder Core operator identity remains pseudonymous with no legal entity mapping.",
"category": "legal",
"event_date": null,
"event_date_precision": "unknown",
"source_type": "self_reported_or_unverified",
"source_tier": 4,
"tier_reason": "Self-reported or unverified third-party signal.",
"verification_status": "disputed",
"confidence": "medium",
"source_ids": [
"SRC-009",
"SRC-008"
]
},
{
"claim_id": "CLM-007",
"claim_text": "Opaque context-window manipulation potential Critics claim developers control the context window that feeds the AI agent, potentially biasing outputs.",
"category": "behavioral",
"event_date": null,
"event_date_precision": "unknown",
"source_type": "self_reported_or_unverified",
"source_tier": 4,
"tier_reason": "Self-reported or unverified third-party signal.",
"verification_status": "disputed",
"confidence": "medium",
"source_ids": [
"SRC-019"
]
}
],
"contradictions_and_disputes": [],
"evidence_gaps": [
{
"question": "X/Twitter coverage is missing for this agent dossier.",
"why_uncertain": "Agents often operate primarily on X/Twitter, but coverage_log has no X surface entry.",
"searched": "Add X / Twitter coverage_log entries with exact post, reply, quote, and search queries plus result status.",
"source_ids": [
"SRC-001",
"SRC-008",
"SRC-009",
"SRC-010",
"SRC-015",
"SRC-018",
"SRC-019",
"SRC-023"
]
},
{
"question": "Farcaster cast/reply coverage is missing for this subject.",
"why_uncertain": "Identity signals include Farcaster/Warpcast, but coverage_log has no Farcaster surface entry.",
"searched": "Add Farcaster/Warpcast coverage_log entry with exact cast/reply/channel queries and result status.",
"source_ids": []
},
{
"question": "No Farcaster post-level citations were collected for live agent behavior.",
"why_uncertain": "Current sources include profile-level Farcaster links but no cast/reply URLs tied to the agent's real-time behavior.",
"searched": "Collect direct Farcaster cast/reply URLs (for example warpcast.com/<handle>/0x...) for live behavior, replies under criticism, and owner-linked activity.",
"source_ids": []
},
{
"question": "Coverage log does not show a dedicated recent-window sweep.",
"why_uncertain": "The dossier includes coverage, but coverage_log does not show explicit last_7_days, last_30_days, or last_90_days passes for live timeline behavior.",
"searched": "Add recent coverage entries with exact queries for last_7_days, last_30_days, and/or last_90_days, especially for handle-led X/Farcaster posts and replies.",
"source_ids": []
},
{
"question": "X query coverage does not explicitly inspect replies or conversation behavior.",
"why_uncertain": "The dossier references X/Twitter, but coverage_log does not show query families for replies, conversations, or quote context.",
"searched": "Run X/Twitter queries containing terms like: replies, with_replies, conversation, quote, quoted, mentions.",
"source_ids": [
"SRC-001",
"SRC-008",
"SRC-009",
"SRC-010",
"SRC-015",
"SRC-018",
"SRC-019",
"SRC-023"
]
}
],
"credentials_and_claims": [
{
"claim": "Launch via Virtuals Protocol AIXBT AI agent launched within the Virtuals ecosystem.",
"verified": true,
"verification_status": "verified",
"confidence": "medium",
"notes": "Observed date: 2024-11 | Source type: web:virtuals.io | Tier rationale: Tier could not be inferred from linked source metadata.",
"source_ids": [
"SRC-006",
"SRC-007"
]
},
{
"claim": "Peak hype cycle Token price reached all-time high near $0.94 during AI-agent narrative boom.",
"verified": true,
"verification_status": "verified",
"confidence": "medium",
"notes": "Observed date: 2025-01 | Source type: web:decrypt.co | Tier rationale: Tier could not be inferred from linked source metadata.",
"source_ids": [
"SRC-007"
]
},
{
"claim": "Security exploit and loss of 55 ETH Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH.",
"verified": true,
"verification_status": "verified",
"confidence": "medium",
"notes": "Observed date: 2025-03-18 | Source type: web:theblock.co | Tier rationale: Tier could not be inferred from linked source metadata.",
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"claim": "Infrastructure autonomy expansion Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.",
"verified": true,
"verification_status": "verified",
"confidence": "medium",
"notes": "Observed date: 2026-03 | Source type: self_reported_or_unverified | Tier rationale: Self-reported or unverified third-party signal.",
"source_ids": [
"SRC-023"
]
},
{
"claim": "Operational security failure Loss of 55 ETH due to dashboard exploit demonstrates vulnerability in surrounding automation infrastructure.",
"verified": false,
"verification_status": "disputed",
"confidence": "high",
"notes": "Source type: web:theblock.co | Tier rationale: Tier could not be inferred from linked source metadata.",
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"claim": "Pseudonymous founder Core operator identity remains pseudonymous with no legal entity mapping.",
"verified": false,
"verification_status": "disputed",
"confidence": "medium",
"notes": "Source type: self_reported_or_unverified | Tier rationale: Self-reported or unverified third-party signal.",
"source_ids": [
"SRC-009",
"SRC-008"
]
},
{
"claim": "Opaque context-window manipulation potential Critics claim developers control the context window that feeds the AI agent, potentially biasing outputs.",
"verified": false,
"verification_status": "disputed",
"confidence": "medium",
"notes": "Source type: self_reported_or_unverified | Tier rationale: Self-reported or unverified third-party signal.",
"source_ids": [
"SRC-019"
]
}
],
"recent_experiments": [
{
"name": "Peak hype cycle",
"first_observed_date": "2025-01",
"status": "observed",
"evidence_type": "primary_social",
"confidence": "medium",
"notes": "Token price reached all-time high near $0.94 during AI-agent narrative boom.",
"source_ids": [
"SRC-007"
]
},
{
"name": "Security exploit and loss of 55 ETH",
"first_observed_date": "2025-03-18",
"status": "observed",
"evidence_type": "primary_social",
"confidence": "medium",
"notes": "Attacker accessed internal dashboard and queued malicious replies, resulting in loss of approximately 55 ETH.",
"source_ids": [
"SRC-016",
"SRC-017"
]
},
{
"name": "Infrastructure autonomy expansion",
"first_observed_date": "2026-03",
"status": "observed",
"evidence_type": "primary_social",
"confidence": "medium",
"notes": "Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.",
"source_ids": [
"SRC-023"
]
},
{
"name": "Infrastructure autonomy expansion Operator indicated AIXBT now has its own server and infrastruc",
"first_observed_date": "2026-03",
"status": "observed",
"evidence_type": "mixed",
"confidence": "medium",
"notes": "Infrastructure autonomy expansion Operator indicated AIXBT now has its own server and infrastructure as part of progressive autonomy initiative.",
"source_ids": [
"SRC-023"
]
}
],
"coverage_log": [
{
"surface": "X / Twitter",
"queries": [],
"date_window": "recovered_from_citations",
"result": "found",
"source_ids": [
"SRC-001",
"SRC-008",
"SRC-009",
"SRC-010",
"SRC-015",
"SRC-018",
"SRC-019",
"SRC-023"
],
"recovery_note": "Exact queries were not preserved in the payload; this row was reconstructed from cited source URLs."
}
]
}