this post was submitted on 16 Jun 2024
214 points (98.2% liked)

Technology

60017 readers
3036 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago
MODERATORS
L3s
[email protected]
[email protected]
L4s
enu
214
New York Times warns freelancers of GitHub repo data breach (www.bleepingcomputer.com)
submitted 6 months ago by [email protected] to c/technology
34 comments fedilink hide all child comments
 
  • The New York Times suffered a breach of its GitHub repositories in January 2024, leading to the theft and leak of sensitive personal information of freelancers.
  • Attackers accessed the repos using exposed credentials, but the breach did not impact the newspaper's internal systems or operations.
  • The stolen data, amounting to 273GB, was leaked on 4chan and included various personal details of contributors as well as information related to assignments and source code, including the viral Wordle game.
you are viewing a single comment's thread
view the rest of the comments
[–] BURN 5 points 6 months ago* (last edited 6 months ago) (1 children)

Yes it is. You can be a pedantic a-hole all you want, but “hacking” includes phishing, social engineering and pretty much any other form of access control circumvention to the general public.

Edit:

Also from the article itself

A 'readme' file in the archive states that the threat actor used an exposed GitHub token to access the company's repositories and steal the data.

Exposed GitHub token is very likely someone messed up and either exposed a token or was victim to an attack that could pull the token. Those are not uncommon and have happened to a lot of companies.