Ai Engineering 3 min read

A Brown Undergrad Mapped AI's Hidden Data Labor Across 31 Countries

Cunyan Ma, a Brown University senior working with its Center for Technological Responsibility, published an interactive map on October 26 linking 13 data-labeling firms, 141 corporate customers, and worker sites in 31 countries, making the supply chain behind AI's training data publicly traceable for the first time.

Brown University published an interactive map on October 26 that makes the least visible part of the AI supply chain traceable: built by Cunyan Ma, a senior concentrating in social analysis and research, working with the university’s Center for Technological Responsibility, Reimagination and Redesign, it connects 13 data-labeling companies to 141 corporate customers and worker sites across 31 countries. The firms involved include the industry’s known names in annotation outsourcing, and the customers span social media platforms, AI labs, retailers, and defense contractors. Her advisor, Suresh Venkatasubramanian, who leads the center and formerly worked in the White House Office of Science and Technology Policy, summarized the thesis in one line: “It’s all humans underneath.”

What the map actually shows

The methodology aggregates existing databases of labeling firms and their clients, adds an original database of delivery centers as a proxy for worker locations, and layers in news reporting on working conditions, with power-mapping used to trace the connections. The tasks being traced are the foundation of every model this site covers: labeling objects in photos and parts of speech in sentences, transcribing speech, rating chatbot responses, drawing tumor boundaries in medical scans, and reviewing violent or abusive content so that AI systems can learn to filter it. The last category is the one that gives the map its moral weight; content moderation work, outsourced to Kenya, Indonesia, Colombia, and elsewhere at wages the map describes only qualitatively as low, is the labor that makes every safety claim in every model card possible, and its psychological cost is documented in the reporting the map aggregates.

Why a map, and why now

The absence of this map was itself a design choice by the industry. AI companies publish model cards and, increasingly, energy and compute disclosures, but the labor supply chain has stayed deliberately opaque to avoid accountability for wages and conditions; Ma’s framing calls it “AI colonialism,” the extraction of low-wage labor from the Global South for Western profit, and notes the opacity is what prevents workers at dispersed delivery centers from even knowing they share an employer. The map is explicitly illustrative rather than comprehensive, which is the right humility: 13 firms and 141 customers is a floor, not a census. But as a public-education artifact it changes what a journalist, a procurer, or a worker can see: the same tracing exercise that Anthropic’s S-1 does for compute commitments, this does for the humans in the pipeline.

What to watch

Three developments would give the map consequence beyond documentation. First, procurement: if enterprise buyers of AI begin asking model vendors for labeling-labor disclosures the way they now ask for carbon accounting, the map becomes an audit standard rather than an advocacy tool. Second, worker organizing: Ma’s stated hope is that dispersed workers can use it to find each other, and cross-border content-moderator organizing has precedent but no shared infrastructure. Third, the semiconductor extension: the center plans to map chip-industry labor next, which would extend the same tracing to the hardware layer whose geopolitical walls, export controls and licensing regimes, dominated this month’s news. The AI industry publishes what it builds; this map is an early attempt to publish who builds it, and the gap between those two disclosures is where the next several years of AI-labor accountability will be fought.

Get Insanely Good at AI

Get Insanely Good at AI

The book for developers who want to understand how AI actually works. LLMs, prompt engineering, RAG, AI agents, and production systems.

Keep Reading

Ai Engineering

gr.Workflow Turns AI Pipelines Into Deployable APIs

Learn how to model, debug, expose, and deploy multi-step AI pipelines with Gradio Workflow and daggr.

Career

OpenAI's Human Trainers Are Being Fired for Using AI to Do Their Jobs

Contractors doing human-feedback work on OpenAI's models, hired through staffing firm Mercor, are being terminated for completing their tasks with AI, per 404 Media, with detection methods that include spotting AI-style punctuation and unnaturally fast work.

Ai Engineering

Broccoli2Shell: the Brotli Bug Gets a Census, and OpenAI Codex Security Gets the Credit

The Broccoli2Shell site published October 25 maps CVE-2026-111497 across every ecosystem: vendored copies in .NET, DuckDB, and Apache Arrow remain unfixed, non-C decoders are clean, and the original bug report came from OpenAI Codex Security.

Ai Engineering

HTTP2Shell: the Brotli Bug Behind PHP2Shell's Naming Season Reaches Node and Python

CVE-2026-111497, an out-of-bounds write in the Brotli decoder bundled with Node.js, escalated October 23 into 'HTTP2Shell' as Aikido confirmed Python HTTP libraries using Brotli are affected too; fixed Node releases shipped October 21 with no workaround for outbound fetch paths.

Ai Engineering

LiteLLM Hit Again: a Stolen-Workflow PyPI Release That Ran on Every Python Start

The official litellm 1.107.0 release on PyPI carried a credential stealer and RCE backdoor on October 21, built through LiteLLM's own signed pipeline after attackers stole GitHub credentials from an exposed internal deployment; the package lived on PyPI for under two hours.