← BREACH ALERTS
HIGH2026-06-05via TheHackerNews

🚨 PCPJack Hijacks 230 AWS, Google Cloud, and Azure Servers for Covert SMTP Relay Network Breach — Data Exposed

PCPJack Hijacks 230 AWS, Google Cloud, and Azure Servers for Covert SMTP Relay Network suffered a data breach. Here's what happened, what data was exposed, and what you should do right now.

ACCOUNTS
HIGH
SEVERITY
DATA TYPES

What Happened

The threat actor known as PCPJack has hijacked cloud servers associated with Amazon Web Services (AWS), Google Cloud, and Microsoft Azure to create a covert SMTP email relay network.

"Compromised business servers across the U.S., Europe, and Asia were quietly converted into SMTP proxies, verified for mail relay capability, and synced to a downstream consumer every five minutes," Hunt.io said in

Impact

  • Affected accounts: Under investigation
  • Data exposed: user data
  • Severity: HIGH
  • Source: [TheHackerNews](https://thehackernews.com/2026/06/pcpjack-hijacks-230-aws-google-cloud.html)
  • What You Should Do

    If you have an account with PCPJack Hijacks 230 AWS, Google Cloud, and Azure Servers for Covert SMTP Relay Network, take these steps immediately:

  • **Change your password** — Use a unique, strong password (16+ chars with mixed case, numbers, symbols)
  • **Enable 2FA** — Turn on two-factor authentication if available
  • **Check your email** — Search for breach notifications from PCPJack Hijacks 230 AWS, Google Cloud, and Azure Servers for Covert SMTP Relay Network
  • **Monitor your accounts** — Watch for unauthorized access on any service where you reused the same password
  • **Scan your site** — If you run a website, [run a free ScanMyVibe scan](https://scanmyvibe.co/scan) to check if your own security headers and configurations protect against common attack vectors
  • Is Your Website Secure?

    Data breaches often exploit weak security configurations — missing Content-Security-Policy headers, misconfigured CORS, exposed API keys. These are exactly the issues ScanMyVibe detects in under 30 seconds.

    [Scan your site free →](https://scanmyvibe.co/scan)

    Timeline

  • 2026-06-05 — Breach reported
  • 2026-06-05 — ScanMyVibe breach alert published
  • Ongoing — Investigation in progress

  • This article is auto-generated by ScanMyVibe's breach monitoring system. Sources are verified but details may evolve as investigations progress. Last updated: 2026-06-05.

    IS YOUR SITE NEXT?

    Scan your website for the same vulnerabilities that cause breaches like this one.

    SCAN FREE — 150+ CHECKS