I believe it might be time to keep 8 week’s worth of cash and food on hand for when the banks stop working and the grocery stores can’t take any EFT payments due to AI cyber war.
This some y2k energy
So it WAS a cyberattack by some script kiddie with a Chromebook during his school lunch hour.
We really need to ban this website as a source.
Just block u/eicker@lemmy.world

I have only been here 2 weeks but I don’t know how your all’s communities haven’t picked up on the OP’s account is a bot…(not directing this at you per se, but just using your post as a jumping off point)
They post articles several times a day, they always immediately post LLM responses to their post, and they always are structured in the same way LLM’s write, complete with the punchy mic drop allegory at the end.
You should create post reports for the mods. This is 100% a bot. The frequency and comment history is blatant.
They do seem like sensationalist garbage
Futurism is the fucking worst. I’m so tired of having to read their click bait articles just to figure out how much they’re lying in the headline
Headline says AI caused the outages, but the article says humans rushed security patches onto ancient infrastructure because AI exposed vulnerabilities. Nothing says cutting edge cybersecurity like taking down the bank yourself before the hackers get a turn.
Hey, sorry not trying to harass you - seeing how I’ve asked you several times - but just hoping for an answer. Are you an actual person?
First, prove to me that you’re a human being and not a stalker. Speaking of which, you can now also follow me easily on Mastodon: https://opinionated.eu/
Then why post the fucking thing!?

There are worse things than a service being unavailable for a few hours, such as data exfiltration, remote code execution, fraudulent transactions, ransomware, etc. I’d rather my bank err on the side of blocking zero-day exploits as quickly as possible.

They are just regurgitating the bullshit article someone posted earlier. This has zero value.
Yeah it’s a bad article. Blaming AI for helping both hackers and security teams find vulnerabilities is ostrich thinking. It gets the villain right but the crime wrong.
Finding security vulnerabilities is one of the few actually legitimate benefits of AI. The fact that it’s exposing companies for having a terrible track record of building broken products is like blaming the smoke detector for going off when people keep setting the kitchen on fire.
The root cause problem is the shoddy “move fast and break things” attitude of so many companies these days. AI’s role has been to let them move even faster and break even more things.
It’s like when a kid keeps going too fast on his bike and breaks his arm, so we buy him a Ducati 999.
The recent NoisyTCP vulnerability had been latent for 11 years. Yeah there’s s lot of AI slop coding out there but not in every case. AI vulnerability scanners are going to leave no stone unturned and eventually that will be a good thing. In the meantime, we all need to brace ourselves for a bumpy ride.
Oh yeah there’s no question they’ve been finding legit bugs, including very old ones that lay undiscovered.
I think there’s a systemic issue lurking in the shadows though, and AI vibe coding is a major contributor to it: large system errors where you can’t point to any particular block of code as responsible. These issues can crop up as the result of many interacting components operating at scale. Cascading failures where many components are behaving correctly when viewed individually but the system as a whole is not.
I’ve tasked LLMs with writing quite a few small-to-medium-sized applications now, and once you get above the level of “programs that could be a single complicated line of perl script”, they absolutely need architectural guidance or they will churn out thousands of lines of crap, complete with working tests that “proves” every component is working as intended.
A few prompts of “No, no, make it like this” at the start, with occasional directed refactorings along the way does wonders for their output. But you need to know where you’re heading and how to get there, otherwise results are definitely not guaranteed.
On one hand, I guess all these app owners will FINALLY fucking patch their shit a little faster.
On the other hand, they seem to be doing a terrible job of testing them before dropping onto production systems. Maybe work that out. You know, make your fancy ai run some tests if you like. Make someone do the testing, sheesh.
Also, I have a hard time believing this much shit went down because all of these companies decided at the same time that patching open vulnerabilities is important.
Not buying it. Something else is going on. Maybe Iran finally got really pissed. Or Russia. Or north Korea. Or Canada. Who knew that being an asshole to the world might come with consequences.
Code security is hard, especially for humans. You need to notice something a bit off between 3+ different pieces of code, and/or have encyclopedic knowledge about quirks of the programming language, compiler, and/or hardware.
We could have been working much harder for secure code, but it would have cost a lot before. Many orders of magnitude more man-hours, substantially higher pay and recruitment for the least pleasant parts of coding. And plenty of apps simply wouldn’t be done.
(Note that you only need one script-kiddy to notice something with an LLM, and then everyone on the internet has to patch it. Plus LLMs make ~everyone able to do this.)
This is decades of technical debt coming back to haunt all at once.
Developers sitting in the back like “remember when you told me it was fine and to just ship it? Well here we are”
I agree with this; I just also note that ignoring the dev and having them dev other things is cheaper (and hence we get more (insecure) things)
















