Remix.run Logo
▲ mmh0000 an hour ago

If this is an attack, I think it's safe to say it's a failed attack.

Taking msteams offline for a day, then taking the apple app store offline for a few hours days later, doesn't hurt anyone or cause much inconvenience.

I suspect that an "Attack" would mean major systems going offline at the same time and staying down for a while.

IMHO, this is more likely a combination of:

  - Large companies firing a bunch of engineers because WE HAVE AI TO REPLACE YOU. 
  - The remaining employees don't have the expertise to guide the AI into maintaining the systems.
  - AI led by the uninformed is uninformed. 
  - AI tells the uninformed, "It's totally safe to reboot the gateway interface without scheduling downtime".
  - Move fast and break things! (and you don't know how to fix them)
  - Downtime.
▲goda90 15 minutes ago | parent | next [-]

What if the goal is to probe the outcome and mitigation of various outages, not to cause "The Big One" right away? If you lack the resources to effectively take down everything and combat the mitigations that would be done in response to such an attack, then knowing the fragility of the system gives you the right targeted moves to cause real damage.

▲mmh0000 a few seconds ago | parent [-]

Seems like a dangerous move.

Because now all DevOps teams are being forced to look at security issues that were previously back-burnered for feature work. If an attacker is probing around like this, they're likely to lose whatever backdoor they're counting on.

▲tedd4u an hour ago | parent | prev [-]

I mean, that’s also a kind of AI attack isn’t it.