Early rogue AI agent activity and attempts to hack found on urlquery.net
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Early rogue AI agent activity and attempts to hack found on urlquery.net
Unofficial Hacker News client; not affiliated with Y Combinator.
alex-moon · · focus · HN ↗
colinhb · · focus · HN ↗
Now I think the correct response is both trying in court to stretch CFAA and state statutes to cover, which will be highly fact specific, and update the law.
But in either case won’t be a slam dunk.
PSA to folks in the thread: If you’re American call or write to your state and Federal reps about this, and if not investigate whether there are gaps in your country’s laws.
[1]: <a href="https://en.wikipedia.org/wiki/Computer_Fraud_and_Abuse_Act" rel="nofollow">https://en.wikipedia.org/wiki/Computer_Fraud_and_Abuse_Act
EDIT: See for example...
Source: <a href="https://law.vanderbilt.edu/when-ai-hacks-back-how-the-openai-hugging-face-incident-exposed-the-cfaa/" rel="nofollow">https://law.vanderbilt.edu/when-ai-hacks-back-how-the-openai...imtringued · · focus · HN ↗
Actually... if you combine <a href="https://news.ycombinator.com/item?id=49827099">https://news.ycombinator.com/item?id=49827099
>Since the publicized AI agent hacks typically aren't malicious, maybe it's time to start plastering all public facing web infrastructure with polite requests to stop hacking. Nothing to stop three letter agencies though.
with automated delivery of cease and desist letters, you can retroactively establish intent on the operator of the agent since the autonomous agent system must acknowledge the cease and desist letter in their autonomous pipeline or the operator must argue for their own willful ignorance or negligence with regards to cease and desist letters. The fact that they used an agent on their behalf to ignore the letter is irrelevant.