Have a sneer percolating in your system but not enough time/energy to make a whole post about it? Go forth and be mid!

Any awful.systems sub may be subsneered in this subthread, techtakes or no.

If your sneer seems higher quality than you thought, feel free to cut’n’paste it into its own post, there’s no quota for posting and the bar really isn’t that high

The post Xitter web has spawned soo many “esoteric” right wing freaks, but there’s no appropriate sneer-space for them. I’m talking redscare-ish, reality challenged “culture critics” who write about everything but understand nothing. I’m talking about reply-guys who make the same 6 tweets about the same 3 subjects. They’re inescapable at this point, yet I don’t see them mocked (as much as they should be)
Like, there was one dude a while back who insisted that women couldn’t be surgeons because they didn’t believe in the moon or in stars? I think each and every one of these guys is uniquely fucked up and if I can’t escape them, I would love to sneer at them.

  • self@awful.systemsEnglish
    17·
    7 个月前

    you can’t just hit me with fucking comedy gold with no warning like that (archive link cause losing this would be a tragedy)

    So my natural thought process was, “If I’m using AI to write my anti-malware script, then why not the malware itself?”

    Then as I started building my test VM, I realized I would need help with a general, not necessarily security-focused, script to help set up my testing environment. Why not have AI make me a third?

    […]

    cpauto.py — the general IT automation script

    First, I created a single junk file to actually encrypt. I originally made 10 files that I was manually copy pasting, and in the middle of that, I got the idea to start automating this.

    this one just copies a file to another file, with an increasing numerical suffix on the filename. that’s an easily-googled oneliner in bash, but it took the article author multiple tries to fail to get Copilot to do it (they had to modify the best result it gave to make it work)

    rudi_ransom.py (rudimentary ransomware)

    I won’t lie. This was scary. I made this while I was making lunch.

    this is just a script that iterates over all the files it can access, saves a version encrypted against a random (non-persisted, they couldn’t figure out how to save it) key with a .locked suffix, deletes the original, changes their screen locker message to a “ransom” notice, and presumably locks their screen. that’s 5 whole lines of bash! they won’t stop talking about how they made this incredibly terrifying thing during lunch, because humblebragging about stupid shit and AI fans go hand in hand.

    rrw.py (rudimentary ransomware wrecker) This was honestly the hardest script to get working adequately, which compounds upon the scariness of this entire exercise. Again, while I opted for a behavior-based detection anti-ransomware script, I didn’t want it to be too granular so it could only detect the rudi_ransom.py script, but anything that exhibits similar behavior.

    this is where it gets fucking hilarious. they use computer security buzzwords to describe such approaches as:

    • trying and failing to kill all python3 processes (so much for a general approach)
    • killing the process if its name contains the string “ransom”
    • using inotify to watch the specific directory containing his test files for changes, and killing any process that modifies those files
    • killing any process that opens more than 20 files (hahaha good fucking luck)
    • killing any process that uses more than 5% CPU that’s running from their test directory

    at one point they describe an error caused by the LLM making shit up as progress. after that, the LLM outputs a script that starts killing random system processes.

    so, after 42 tries, did they get something that worked?

    I was giving friends and colleagues play-by-plays as I was testing various iterations of the scripts while writing this blog, and the consensus opinion was that what I was able to accomplish with a whim was terrifying.

    I’m not going to lie, I tend to agree. It’s scary that was I was able create the ransomware/data wiper script so quickly, but it took many hours, several days, 42 different versions, and even more minor edits to fail to stop said ransomware script from executing or kill it after it did. I’m glad the static analysis part worked, but that has a high probability of causing accidental deletions from false positives.

    I just want to reiterate that I had my AI app generate my ransomware script while I was making lunch…

    of course they fucking didn’t

    • Soyweiser@awful.systemsEnglish
      13·
      7 个月前

      I was giving friends and colleagues play-by-plays as I was testing various iterations of the scripts while writing this blog, and the consensus opinion was that what I was able to accomplish with a whim was terrifying.

      This is correct, but not for the reasons they think it is terrifying. Imagine one of your coworkers revealing they are this bad at their job.

      “guys guys! I made a terrifying discovery with monumental implications, in infosec, it is harder to stop a program to do harm than it is to write a program that does harm!” (Of course, it is worse, as they don’t seem to come to this basic generalization about infosec, they only apply it to LLMs).

    • V0ldek@awful.systemsEnglish
      10·
      7 个月前

      the consensus opinion was that what I was able to accomplish with a whim was terrifying.

      Man Discovers Running Random Sys Commands in Python Can Do Bad Things.

      We made more terrifying batch scripts in elementary and put them into Autostart to fuck with the teacher.

      • froztbyte@awful.systemsEnglish
        6·
        7 个月前

        When I was a wee youngin’, I had an exponential copy one in an org-wide NT autostart (because, y’know, that’s what kind of stupid shit you do when you’re young and like that)

        It took weeeeeks but when it finally accumulated enough it pretty much tanked the entire network. It was kinda hilarious seeing how lost the admins were in trying to figure it out

        Probably one of my first lessons in learning some particular things about competencies

    • froztbyte@awful.systemsEnglish
      8·
      7 个月前

      I’ve seen better shellcode in wordpress content injection drivebys

      “Everyone also agreed with me that this was terrifying” fuck outta here

      And I bet this stupid thing will suddenly be all over infosec sphere within days…

    • pyrex@awful.systemsEnglish
      6·
      7 个月前

      I read a few of the guy’s other blog posts and they follow a general theme:

      • He’s pretty resourceful! Surprisingly often, when he’s feeling comfortable, he resorts to sensible troubleshooting steps.
      • Despite that, when confronted with code, it seems like he often just kind of guesses at what things mean without verifying it.
      • When he’s decided he doesn’t understand a thing, he WILL NOT DIG INTO THE THING.

      He seems totally hireable as a junior, but he absolutely needs the adult supervision.

      The LLM Revolution seems really really bad for this guy specifically – it promises that he can keep working in this ineffective way without changing anything.

      • zogwarg@awful.systemsEnglish
        9·
        7 个月前

        My conspiracy theory is that he isn’t clueless, and that his blogposts are meant to be read by whoever is his boss. In the case of using LLMs for automatic malware and anti-malware.

        “Oh you want me to use LLMs for our cybersecurity, look how easy it is to write malware (as long as one executes anything they download, and have too many default permissions on a device) using LLMs, and how hard it is to do countermeasures, it took me over 42 (a hint?) tries and I still failed! Maybe it’s better to use normal sandboxing, hardening and ACL practices, in the meantime to protect ourselves from this new threat, how convenient it’s the same approach we’ve always taken”