ZeroHour

Search: “commit”

47 stories

50,000 Stripe Secrets Leaked in Public Code

Over 50,000 Stripe merchant API keys leaked via public code and logs; 659 merchant accounts' data offered on trading forum.

Ransomnews researchers identified over 50,000 unique Stripe merchant API keys exposed in public GitHub repositories, GitHub Actions logs, and misconfigured web servers. A dataset on a data-trading forum dated August 18, 2026 contained live keys for 659 merchant accounts plus roughly 35 GB of customer and payment data. Researchers demonstrated a leaked key enabled accessing customer lists, creating fraudulent payment links, and making test charges within 17 hours. Stripe itself was not compromised; over 3,000 misconfigured web servers revealed Stripe-related strings, with about 12% containing working keys.

Security Affairs · 28d agoData breach in the wild

Surfshark Systems Targeted by Hackers

Surfshark discloses hackers accessed a misconfigured internal test server; no user data or VPN services affected.

Surfshark discovered on August 31 that a threat actor accessed an internal test server exposed to the internet through misconfiguration, obtaining some system binaries and internal configurations. Build-related credentials committed to code history were rotated, and an isolated content optimization VPS was also accessed, though no user data, encryption keys, or browsing activity were exposed. The company contained the system, rotated credentials, and announced an independent security audit.

SecurityWeek · 5d agoData breach in the wild 2 sources

Mozilla Revokes Firefox and Thunderbird Linux Signing Key After Key Lands in Private Repo

Mozilla revoked the Firefox and Thunderbird Linux RPM signing subkey after an unencrypted copy landed in a private repo; no unauthorized access found.

Mozilla revoked the OpenPGP signing subkey (fingerprint 09BE ED63 F346 2A2D FFAB 3B87 5ECB 6497 C1A2 0256) used for Firefox and Thunderbird Linux downloads after an unencrypted copy was committed to one of its private repositories, citing reason code 2, 'key material has been compromised.' Audit records showed no sign of unauthorized access, and a replacement subkey (827E 6586 0867 9618 CD34 9F93 678E 455D 7676 7AA3) valid until August 5, 2028 was published. Users who verify signatures manually or install from Mozilla RPM packages may need to import the new key and remove the old one. The rotation came roughly seven months ahead of Mozilla's usual two-year subkey cycle.

The Hacker News · Aug 11, 2026Data breach