Over the past 72 hours, a wave of panic swept through my Telegram trading groups. Screenshots of indexed Google results started circulating: Claude conversations containing wallet addresses. Perplexity threads revealing trading algorithms. This wasn't a targeted hack — it was a design failure. Noindex tags missing. Robots.txt ignored. The very tools we trusted to analyze markets turned into public ledgers of our strategies.
Trust the hands, not just the charts. Right now, those hands might be holding your private discussion.
The Context: Two Platforms, One Blind Spot
Both Claude (Anthropic) and Perplexity AI offer a “share link” feature — a seemingly innocuous way to pass an AI-generated analysis to a colleague. But here’s the catch: neither platform automatically applied the noindex meta tag to those links. Google’s crawlers, hungry for new content, treated them as public pages. By the time anyone noticed, millions of conversations were indexed.
According to an investigation by Protos (first reported on Reddit in late July 2025, then escalated in September), Claude’s shared artifacts and Perplexity’s shared threads were discoverable via simple Google dorks. The timing is brutal: we’re in a bear market, survival mode. Suddenly, your thesis on the next L2 play is public. Your due diligence on a DeFi protocol? Public. Your seed phrase discussions? Let’s hope you didn’t paste those.
Claude moved fast. As of this writing, most Claude results have been de-indexed — Google shows zero indexed artifacts. Perplexity? Still wide open. Their share interface reads “Anyone with the link can view” — implying control, but failing to mention “anyone on the internet, including Google’s bots.” That’s not a bug; it’s a betrayal of trust.
The Core: How the Leak Hits Crypto Harder
This isn’t just about privacy; it’s about edge. In crypto, information asymmetry is the difference between profit and liquidation. Here’s what was actually exposed:
- Credentials & API keys: Several indexed conversations included login credentials for exchanges and wallets.
- Internal project communications: Startups using Perplexity for strategy planning accidentally shared vesting schedules and tokenomics details.
- Trading command logs: Traders copying and pasting smart contract addresses or using AI to analyze on-chain data — now visible to competitors.
The technical root is straightforward: shared links were stored on the platform’s domain under predictable URL patterns. Perplexity, in particular, used a static page structure that allowed crawlers to traverse the directory. No CAPTCHA. No authentication. Just a bare HTML page waiting to be scraped.
I’ve been in this space since 2018. I’ve seen ICO whitepapers leak, Discord servers get raided. But this is different — it’s a firehose of high-signal data flowing directly into search engines. If you’ve ever shared a Claude artifact or a Perplexity thread with anyone, assume it’s public.
The Contrarian: Why This Might Not Be Fixed Soon
Most analysts are saying “just add noindex, problem solved.” That’s true for future links. But here’s the contrarian twist: the damage is already done, and the fix is fragile.
First, all major search engines cache indexed pages. Even if Perplexity adds noindex tonight, those results will remain in Google’s cache for days or weeks. Second, the Wayback Machine and third-party scrapers have already archived thousands of these pages. Once data touches the internet, it never truly disappears.
But here’s the real blind spot: many crypto projects rely on AI for operational tasks — drafting governance proposals, summarizing research, even generating code for smart contracts. A leaked smart contract draft could be front-run by malicious actors. The retail trader thinks “I’m just saving my analysis.” The smart money knows they’re handing their edge to the public.
Secondly, the incident underscores a deeper issue: the AI industry’s design philosophy defaults to open sharing. That’s fine for public knowledge, but deadly for financial secrets. Until platforms adopt a “private by default, share by explicit manual consent” model, this will repeat. OpenAI had a similar leak in July 2025. Claude fixed it quickly. Perplexity still hasn’t. The pattern is clear — but the industry isn’t learning fast enough.
The Takeaway: What You Do Now
If you’re a crypto trader or a project lead using these tools:
- Revoke all shared links immediately. Most platforms let you delete individual shares. Do it now.
- Search your own links. Use
site:perplexity.aiandsite:claude.aiwith your username or project name. If you find anything, it’s already indexed. You can request removal via Google Search Console, but it’s a race against time. - Shift to encrypted alternatives. For sensitive discussions, use platforms with end-to-end encryption like Signal or Matrix. Never paste wallet details into AI chat logs.
- Treat AI sharing as a public forum. Assume anything you type into a shared link can be seen by everyone — because it can be.
Community first, coins second. Always. The real value isn’t the code or the strategy; it’s the trust we build through disciplined ops. A leak like this doesn’t just cost money — it costs reputation.
Trust the hands, not just the charts. Make sure those hands aren’t typing your secrets into a publicly indexed URL.
Follow the people, follow the profit. But first, follow the security.