all 4 comments

sorted by: hot top controversial new old
[–] 28 points 9 months ago

This is just poor security. Not like in TV/Movies where an "AI" was found "breaking layers of firewalls and encryption" or whatever 🤣

Somebody fucked up. Plain and simple.

  • source
  • [–] 15 points 9 months ago* (2 children)

    Y'all obviously lead with AI and you're bad at propaganda.

    The attackers initially gained access by stealing valid test credentials from public Amazon S3 buckets. The credentials belonged to an identity and access management (IAM) user with multiple read and write permissions on AWS Lambda and restricted permissions on AWS Bedrock

    Run your shit against tenable once in a while.

  • source
  • hideshow 2 child comments
  • [–] 5 points 9 months ago (1 child)

    The point of the article is to show that with help of AI, attacks can be executed faster, which means higher success chance for getting more data/damage as you're essentially running against time.

    How long would all this have taken without automation?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 9 months ago

    According to you all shorter because AI is simultaneously garbage propping upa bubble, so my sarcastic answer is it's slower.

    That being said I know I could detect and scan, with nessus/snyk/security hub and detect the issue inside of 5 minutes. Probably another half hour to hour for a proper pen tester to send an AWS exploit package at it and own the rest within an hour or two. 

    How many people do you think catch exploits in the first day or even week or month of a hack? I've got some news for you, its only the companies who really need their shit together and have a strong opssec team. They ain't going deleting buckets. They sit on it for months and years in most post mortem.

  • source
  • parent
  • 5 comments in c/pulse_of_truth@infosec.pub view that post
    [–] 7 points 9 months ago

    Given how much AWS is pushing vibe-coding, we're now in the Leopard-Face-Eating territory.

  • source
  • [–] 11 points 9 months ago (3 children)

    Vibe hacking is the future. Really.

  • source
  • hideshow 3 child comments
  • [–] 7 points 9 months ago (1 child)

    It’s going to be vibe hackers hacking vibe coded systems. Caaaaaant waaaaaiiiiit!

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 9 months ago

    From the report that's the source of this Register article (emphasis added):

    The threat actor infiltrated the victim’s environments using valid test credentials stolen from public S3 buckets. These buckets contained Retrieval-Augmented Generation (RAG) data for AI models , and the compromised credentials belonged to an Identity and Access Management (IAM) user that had multiple read and write permissions on AWS Lambda and restricted permissions on AWS Bedrock. This user was likely intentionally created by the victim organization to automate Bedrock tasks with Lambda functions across the environment.

    It is also important to note that the affected S3 buckets were named using common AI tool naming conventions, which the attackers actively searched for during reconnaissance.

    https://www.sysdig.com/blog/ai-assisted-cloud-intrusion-achieves-admin-access-in-8-minutes

  • source
  • parent
  • [–] 4 points 9 months ago

    It’s absolutely one of the strongest applications of LLMs right now.

    Very interested to see how things develop long-term though, since theoretically we should start seeing red team tools developed that can close the holes an attacker would be hunting. Granted, I think we’ll need at least another five years for true high-quality pentest agents, and offense will have the upper hand in the cat & mouse until then.

  • source
  • parent
  • 2 comments in c/cybersecurity@infosec.pub view that post
    [–] 12 points 9 months ago (1 child)

    If your operation can be hacked by Clippy on Acid then it was not exactly Fort Knox to begin with.

  • source
  • hideshow 1 child comment