• tetris11@feddit.uk
    link
    fedilink
    English
    arrow-up
    6
    ·
    15 hours ago
    echo "H4sIAAAAAAAAA1OIJwpw2SgE5KQmFqcqOCaXZJYllqQq+GTmlVYolGeWZGTmKRgbKKQkVhYr2HEp\
    6BIFuBSQgEaMviZUQCM+X6EGJqmvgGDHABHULQoIIQjQzEcYp18DNh+hEaiuBirDBQApvkoY7gAAAA==" \
     | base64 -d | gzip -d
    
    • sp3ctr4l@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      14 hours ago

      Pretty sure I’m not gonna be running anything involving “gzip -d”, seems like probably a bad idea, lol.

        • sp3ctr4l@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          3
          ·
          12 hours ago

          Ahah, ah… yeah, yep, uh, you got me, stinkin little coward over here.

          But uh hey, I could always try that out on your PC, right big bro?

        • sp3ctr4l@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          12 hours ago

          Is that even some particular kind of actual instruction set, or just gibberish that would cause something like a fork bomb?

          I guess it is a base-d virus though, 64 ways to sunday…

          • tetris11@feddit.uk
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            5 hours ago

            For it to be anything executable you’d have to pipe it into bash again to evaluate it

            For it to be a zip bomb of any merit, the gzipped contents would have to have more than a few bytes