Exhibit D: The Alkatraz Front
Buried deep in the server archives is a name tied to one of Jailbreak’s most infamous custom maps:
jb_alkatraz
Officially, the map was “community-made.”
Unofficially, the fingerprints tell another story.
🏗
The Builder That Wasn’t There
- Early test versions of jb_alkatraz were uploaded under throwaway accounts
- Those accounts shared IP behavior and dev habits matching Pinecone’s activity window
- Pinecone was “inactive” during every major development milestone — yet always present when updates went live
The Donor Pipeline
Here’s where it gets uncomfortable.
Internal donation logs (fictional) suggest Panda donor funds were routed through:
- “Map optimization costs”
- “Asset licensing”
- “Emergency server fixes”
But no such fixes were ever deployed.
Instead, the funds allegedly flowed into:
- Alt accounts
- Private inventories
- Quiet rank boosts tied back to Pinecone-adjacent profiles
Why Panda?
Panda’s donor system was trusted.
Automated.
Rarely audited.
Perfect cover.
jb_alkatraz, with its complex layout and constant “maintenance,” became the ideal laundering mechanism — a map that was always “unfinished,” always needing just a little more support.
The Truth
Pinecone didn’t just play Jailbreak.
Pinecone built infrastructure — maps, systems, excuses — all to move donor money without ever touching the spotlight.
A prison map.
A financial funnel.
A perfect irony.
Alkatraz wasn’t designed to keep people in.
It was designed to move things out.
