this post was submitted on 14 Jul 2024
588 points (98.5% liked)

Technology

59598 readers
3147 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 1 year ago
MODERATORS
L3s
[email protected]
[email protected]
L4s
enu
588
Disney hack leads to 1.2TB of Slack communications leaked online (stackdiary.com)
submitted 4 months ago by skilledtothegills to c/technology
58 comments fedilink hide all child comments
 

In a significant data breach, hacktivist group NullBulge has infiltrated Disney's internal Slack infrastructure, leaking 1.2TB of sensitive data. This breach, posted on the cybercrime platform Breach Forums on July 12, 2024, exposes many of Disney's internal communications, compromising messages, files, code, and other proprietary information.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 39 points 4 months ago (2 children)

Plus in their blog post they mention that they haven't read through most of the leaks themselves so they don't even know what kind of info they might be posting about potentially unrelated people, in an attack on "AI" that won't stop disney even a little bit. Like, I understand the desire to help creative people but I don't see how this is doing that

[–] [email protected] 21 points 4 months ago (1 children)

If you're a grey-hat/chaotic-good hacker intent on exposing corporate greed or whatever, with a cache like that, you've got a couple options....either release inmediately, or review the data to minimize collateral damage and release.

If the intent was to help people, and there was no driving force to release immediately, then they should've waited and reviewed the data.

I really worry if this is going to lead to my overly-ambitious infosec group putting the kibash on our unofficial/shadow-IT (fully internal) MatterMost.

[–] hahattpro 2 points 4 months ago

Review the data cost your time (which is work time, could be transfer into money).

So, better release it all.