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.

  • Evotech@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    An export like this does not include private slack channels from what I know of Slack design and export mechanisms

    • paf0@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      I think it would depend on the level of the account. They have that feature for compliance reasons in heavily regulated industries.

      • Evotech@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        4 months ago

        Kinda, but not even admin accounts can view/export private channels they are not a member of.

        I don’t think that’s even a feature

        • bamboo@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 months ago

          I had to manage a Slack migration to another org we were merging with. As the owner, normally I couldn’t even see the names of private channels, but when it came down to the migration, upgrading the account to Business+ tier, the full export included everything (private channels and DMs), which we imported into the new org.

          Slack sends notifications to all Admins that the export was happening, and i’ve only seen that notification once after using Slack for 10 years.

          • Petter1@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 months ago

            😮I bet there is some spicy stuff in the DMs of companies with 1000+ people