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.
So we gonna finally accept that maybe all these cloud services aren’t that secure
Internal slack infrastructure
Taking this part of the description at face value anyway, this sounds like the opposite of the cloud.
That being said, I still agree with the statement
I don’t think Slack has a self hosted version, and does not offer IP allow listing. There’s nothing preventing someone to go to https://disney.slack.com/. I think when they say “internal” they mean for internal employees, and not like a thing for fans.
I think when Disney demands an internally-hosted version of your product, then the sales team tells engineering that they’ll provide one, and mark the price up accordingly. That kind of thing doesn’t appear on the external listing for everyone else.
They do. You pay extra for it. You have to have apache or a web server configured for it, and a lot of space. Source: I configured one like 4 years ago.
Good. Based for Nullbulge that they have released the source for free. Their motive is to put pressure on Disney due to their wrongdoings against creative artists.
I don’t remember, but here is their website with a magnet link for the source: https://nullbulge.se/blog.html
Huh, I looked through the website of the hacking team and they use slurs and talk about posting on 4chan, it’s not a great look for a group trying to get on the good side of creative peoples imo
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
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.
also while I am on my soap box, ai-bro and crypto-bro are gendered insults and we should do better
In a shocking move, the wage slaves found that their bosses know that they are severely underpaid.
So many passwords will be in there. And cat photos.
Passwords and lotsa creds. I know an infra engineer who stores all of the keys to the projects he’s involved in his message to self Slack. When I asked him about it he told me ‘when I found out that the company billed my time 5x my salary to clients I stopped caring’ and I was like OK that’s fair ¯\_(ツ)_/¯
Depends. Our engineering slack (Few thousand members) doesn’t contain secrets for a few reasons:
- Secret scanning
- We have a /secret bot that will take your secret, store it securely, and then present a GUI for each person with access to display that secret “for just that person”. And then after a set period of time it’s made inaccessible, and wiped from the infra.
- Training and knowledge transfer on secret security
This has been incredibly effective. Especially the secret bot.
Turns out that the problem with people sharing secrets is just a matter of convenience. If you make a secure way convenient then everyone tends to just use it by default.
