CISA Advisories

Pentagon Leaks 2.8M Records 🏛️ + 543K Live Keys Left on GitHub 🔑

Two stories this week share the same uncomfortable lesson: sensitive data stays dangerous long after it slips out. One hit millions of people through a government breach. The other shows how many businesses are leaving the keys to their systems lying around in public.

The Pentagon Breach That Spilled 2.8 Million People's Data

The Pentagon has confirmed that a hacking campaign lasting several months exposed records on 2.8 million living people. The stolen data came from the Defense Manpower Data Center and includes Social Security numbers, home addresses, demographic details, and military job specialties. Separately, the hacking group ShinyHunters claims it took FBI employee records, including which staff investigate China and Russia. Officials still haven't said how the attackers got in or whether a ransom was demanded. If you or a family member has served in the military, watch for official notices, consider freezing your credit, and be extra suspicious of calls or emails that reference your service history.

Read more

543,699 Working Passwords and Keys, Sitting in Plain Sight

Security firm Truffle Security scanned 224 million public GitHub projects and found 543,699 passwords and access keys that still worked. The typical one had been exposed for over two years, and the oldest dated back to 2009. GitHub's built-in protection blocks about half of the common types, but it misses things like database passwords and Google Cloud keys, which make up most of the live leaks. The big takeaway: companies that cancel and replace a leaked key are safe, while those that don't are leaving the door wide open (more than 69,000 Google Cloud keys still worked). If your team writes code, scan your repositories for secrets and make "revoke and replace" a standard step whenever one leaks.

Read more

Stay ahead of threats with GOCO Security at gocosecurity.com.

Comments