Back to overview
Confidence MediumMay 20, 2026github.com

GitHub Confirms TeamPCP Hack of Internal Environment

PatternExternal actor · Hacking · Confidentiality impact

GitHub confirmed that TeamPCP hackers breached a limited internal environment connected to the broader TanStack supply-chain campaign. While customer repositories and production systems remained secure, the incident raised concerns over software supply-chain integrity and developer platform security. The threat actor group TeamPCP claimed responsibility for stealing approximately four thousand developer code repositories and intended to sell the stolen internal source code.

Signal date
May 20, 2026
Updated
Jun 29, 2026
Confidence
Medium
Sources
2 sources
github.com logo

Github

Sector
Information
Signals
1 linked

Signal context

First seen: May 20, 2026

Last updated: Jun 29, 2026

Status: Public signal

Key points

  • GitHub confirmed a breach of a limited internal environment by TeamPCP hackers.
  • The incident was linked to the broader TanStack supply-chain campaign.
  • Approximately 4,000 developer code repositories were allegedly stolen.

Signal analysis

Beta

This analysis groups the signal by industry, likely incident action and impacted security area. It helps compare this signal with other published signals without treating the labels as final determinations.

Affected organization
Github logo
Github

Sector: Information

Likely country: Location not provided

Estimated
Threat source
Hacking activity

Watch internet-facing systems, credential abuse and exploit activity.

  • Source type: outside the affected organization
Business impact
Potential data or process integrity risk

Impact area: Confidentiality, Integrity

Likely asset: User or customer data

Trend context
69 signals with similar action pattern
  • 26 signals in the same sector
  • 90 signals with the same likely impact area
  • 1 signal linked to this organization/domain
Mentioned entities
GithubData DisclosureGitHub Confirms TeamPCP Hack ofInternal Environment GitHubTeamPCPTanStackWhileGitHubApproximately

External sources

Related signals

Grouped by why the signal is relevant.

nifty.com logoNiftyJun 28, 2026
Same sectorSame action patternSame impact area

NIFTY Corporation Affected by KDDI Corporation Data Breach

NIFTY Corporation, a Japanese internet service provider, was impacted by a data breach originating from an email system provided by KDDI Corporation. Threat actors gained unauthorized access to this shared system by exploiting a vulnerability in third-party software. This led to the potential exposure of up to 14.2 million email addresses and passwords across all affected ISPs. NIFTY Corporation customers' email addresses and passwords may have been compromised.

biglobe.ne.jp logoBiglobeJun 28, 2026
Same sectorSame action patternSame impact area

BIGLOBE Inc. Affected by KDDI Corporation Data Breach

BIGLOBE Inc., a Japanese internet service provider, was impacted by a data breach originating from an email system provided by KDDI Corporation. Threat actors gained unauthorized access to this shared system by exploiting a vulnerability in third-party software. This led to the potential exposure of up to 14.2 million email addresses and passwords across all affected ISPs. BIGLOBE Inc. customers' email addresses and passwords may have been compromised.

stnet.co.jp logoStnetJun 28, 2026
Same sectorSame action patternSame impact area

STNet, Inc. Affected by KDDI Corporation Data Breach

STNet, Inc., a Japanese internet service provider, was impacted by a data breach originating from an email system provided by KDDI Corporation. Threat actors gained unauthorized access to this shared system by exploiting a vulnerability in third-party software. This led to the potential exposure of up to 14.2 million email addresses and passwords across all affected ISPs. STNet customers' email addresses and passwords may have been compromised.

kddi-web.com logoKddi WebJun 28, 2026
Same sectorSame action patternSame impact area

KDDI Web Communications Customer Data Affected by KDDI Email System Breach

KDDI Web Communications, a subsidiary of KDDI, was impacted by the data breach in KDDI Corporation's email system, disclosed on June 28, 2026. The incident, caused by a third-party software vulnerability, led to the potential exposure of up to 14.2 million email addresses and passwords belonging to customers across six Japanese ISPs, including KDDI Web Communications.

jcom.co.jp logoJcomJun 28, 2026
Same sectorSame action patternSame impact area

JCOM Co., Ltd. Affected by KDDI Corporation Data Breach

JCOM Co., Ltd., a Japanese internet service provider, was impacted by a data breach originating from an email system provided by KDDI Corporation. Threat actors gained unauthorized access to this shared system by exploiting a vulnerability in third-party software. This led to the potential exposure of up to 14.2 million email addresses and passwords across all affected ISPs. JCOM customers' email addresses and passwords may have been compromised.

polymarket.com logoPolymarketJun 28, 2026
Same sectorSame action patternSame impact area

Polymarket Suffers $3 Million Crypto Drain via Third-Party Vendor Compromise

Prediction market platform Polymarket disclosed a breach where hackers compromised a third-party vendor. The attackers injected malicious code into the Polymarket website for some users, leading to the draining of approximately $3 million in pUSD (USDC-backed) from at least 11 user wallets. The stolen funds were subsequently swapped and moved to Ethereum. Polymarket has contained the incident, committed to full refunds for affected users, and is in the process of notifying victims. This incident highlights supply-chain vulnerabilities in web frontends and crypto platforms.