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.

  • Glitchvid@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    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.