Edit: The post was probably heavily AI written and contains mistakes to that effect, which is unfortunate. The data in general is still interesting though.

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    3 days ago

    It’s possible it was something misconfigured, a poorly-written script, or a bug in some software causing unexpected behavior. At the scale of the Internet, all of those are very possible.

    It could also be the Internet equivalent of a numbers station.

    • Glitchvid@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      It’s was a pretty specific non standard port on UDP. It’s not even doing proper scanning since the byte sequence used isn’t one that would trigger a response challenge/ack. My guess is someone trying to DOS using an older byte sequence that used to choke/kill the server software on older versions.