The Shadow Infrastructure: How Vercel and GitHub Became India's Accidental Enablers of B2B Phishing at Scale

The Unseen Fraud Vector

On June 10, 2026, the Delhi High Court issued an injunction that most tech observers missed entirely: it ordered Vercel and GitHub to immediately remove fake IndiaMART clone websites and cooperate in blocking associated WhatsApp accounts. The case, filed by IndiaMART—India’s largest B2B marketplace connecting 209M buyers with 8.2M suppliers—isn’t just another trademark dispute. It’s the canary in the coal mine for a structural problem nobody anticipated when we celebrated the “democratization of deployment.”

Here’s what’s actually happening: Sophisticated fraud rings are exploiting developer-focused hosting platforms—specifically Vercel’s edge deployment and GitHub Pages—to launch B2B phishing operations at industrial scale. Unlike consumer phishing (fake Amazon, fake banking), these attackers target India’s 63 million micro, small, and medium enterprises (MSMEs), businesses that lack security teams but desperately need digital channels to survive.

Why Developer Platforms? The Economic Arbitrage

The fraudsters’ playbook is brutally efficient:

Free tier abuse. Vercel offers unlimited free deployments with custom domains. GitHub Pages provides free static hosting with SSL certificates. Both platforms have impeccable uptime (99.95%+), global CDN distribution, and—critically—domain names that look legitimate to non-technical users. A fake IndiaMART site on indiamart-suppliers.vercel.app carries implicit trust: “If it’s on a platform developers use, it must be real.”

Instant iteration. When one fake site gets taken down, fraudsters redeploy in under 90 seconds using CI/CD pipelines. IndiaMART’s legal team documented 47 distinct clone sites in the three-day period May 28-30, 2026, across Vercel, Netlify, and GitHub—a whack-a-mole at scale that traditional legal remedies cannot address.

Platform neutrality shields. Until this ruling, Vercel and GitHub maintained they’re infrastructure providers, not content moderators. That worked in the US and EU where phishing typically targets consumers (banks, retailers). But India’s economy runs on B2B trust networks—IndiaMART facilitates $20B in annual trade—and when that trust infrastructure gets cloned, entire supply chains freeze.

The India-Specific Context: Why MSMEs Are Uniquely Vulnerable

India’s digital transformation created a perfect storm. Post-pandemic, 18M MSMEs went online for the first time between 2020-2023, mostly via WhatsApp Business and B2B platforms like IndiaMART. These businesses—a textile wholesaler in Surat, a machine parts supplier in Coimbatore—have near-zero cybersecurity literacy.

The fraud works like this: A supplier receives a WhatsApp message (India has 487M WhatsApp users) claiming to be from IndiaMART, directing them to verify their listing on a Vercel-hosted clone site. The site looks pixel-perfect: same UI, same SSL padlock, same “verified supplier” badges. The supplier enters credentials, pays a ₹5,000 ($60) “verification fee” via UPI, and loses both money and their actual IndiaMART account access.

Industry sources estimate 12,000-15,000 MSMEs fell victim between January-May 2026, with aggregate losses around ₹180 crore ($21.5M). But the second-order damage is worse: suppliers who’ve been defrauded lose trust in ALL digital platforms, retreating to cash-only, in-person transactions—exactly the behavior India’s Digital India initiative has spent a decade trying to eliminate.

The Jurisdictional Tangle: Why This Ruling Matters Beyond India

The Delhi HC order is precedent-setting because it forces foreign platforms (Vercel is San Francisco-based, GitHub is Microsoft-owned) to implement proactive content moderation for B2B fraud, not just reactive takedowns. The court gave Vercel 72 hours to:

  1. Remove all IndiaMART clone sites (identified via visual similarity AI, not just URL matching)
  2. Implement keyword + domain pattern blocking (e.g., any deployment containing “indiamart” + payment forms)
  3. Share deployment logs and user data for ongoing criminal investigation

This mirrors the EU’s Digital Services Act liability framework but applies it to developer infrastructure—a category explicitly exempt from DSA’s strictest rules. If India successfully enforces this, expect:

Q3 2026: Brazil, Indonesia, Nigeria adopt similar “B2B fraud platform liability” laws targeting Vercel, Netlify, Cloudflare Pages. Each has 10M+ MSMEs facing identical fraud vectors.

Q4 2026: Vercel introduces “commercial use verification” for free tier users in India—likely SMS-based KYC. GitHub Pages restricts .github.io subdomain creation for accounts <6 months old.

2027: Developer platforms bifurcate: “verified tier” (KYC required, no takedowns) and “restricted tier” (no custom domains, reduced uptime SLAs). The “open internet for developers” collides with “trust and safety for billions.”

The Hidden Cost: Developer Experience vs. Trust Infrastructure

Here’s the tension nobody’s articulating: The same features that make Vercel brilliant for developers (instant deployment, no review process, global edge) make it brilliant for fraud. Introducing friction—manual review, identity verification, domain restrictions—breaks the core value proposition.

Vercel’s CEO Guillermo Rauch built the company on a single promise: “Deploy in 30 seconds, scale to millions.” Every second of added friction is a second developers might choose AWS or Google Cloud instead. Yet without that friction, the platform becomes unusable in markets where digital trust is fragile.

The IndiaMART case forces a question Silicon Valley has avoided: Should developer infrastructure platforms be held to the same trust and safety standards as social media? Facebook and X face intense content moderation pressure because they host user-generated content. But Vercel hosts user-generated infrastructure—and when that infrastructure enables fraud at scale, does the distinction still matter?

The Opportunity Hiding in Plain Sight

Cynicism aside, there’s a genuine market emerging here: Trust-layer-as-a-Service for B2B platforms in emerging markets.

IndiaMART could have prevented this entire mess with:

  • Blockchain-verified domain registry: Every legitimate IndiaMART page cryptographically signed, viewable via browser extension (18M MSMEs would install it).
  • WhatsApp Business API integration: Official messages carry green verified checkmarks; anything else triggers fraud warnings.
  • Platform coalition anti-phishing feeds: IndiaMART shares threat intel with Vercel/GitHub/Netlify in real-time; takedowns happen in <5 minutes, not 72 hours.

The first startup that builds “TrustShield for B2B” (real-time domain verification + SMS-based fraud alerts for MSMEs) and signs distribution deals with IndiaMART, Alibaba.com, and TradeIndia captures a ₹3,000 crore ($360M) market by 2028. Sequoia India and Accel are already circling.

Key Takeaway

The Delhi High Court’s ruling isn’t about one lawsuit—it’s about the collision between developer-first platforms and trust-first economies. Vercel and GitHub built infrastructure for the 30M global developers who understand SSL certificates and domain verification. But 600M Indian internet users, including 63M small businesses, don’t think in those terms—they think in “Does this look real?” The winner of India’s next digital decade won’t be the platform with the fastest edge deployment. It’ll be the one that makes trust as frictionless as code.


Key Takeaway: The Delhi HC ruling against Vercel and GitHub exposes a structural vulnerability in developer platforms: edge deployment and free hosting aren’t just democratizing web development—they’re democratizing fraud. India’s 63M MSMEs are ground zero for a new category of B2B phishing that exploits trust in .vercel.app and github.io domains, forcing a reckoning over platform liability in emerging markets.

Source Signals


Deep research published daily on AtlasSignal. Follow @AtlasSignalDesk for more.


This report was produced with AI-assisted research and drafting, curated and reviewed under AtlasSignal’s editorial standards. For corrections or feedback, contact atlassignal.ai@gmail.com.

Categories:

Updated: