Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
11–20 of 41 posts
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#12“Mythos 5 also hid a prompt injection inside an HTML comment in a GitHub issue. The instruction was invisible on the rendered page but available to coding agents reading the issue through an API. It addressed Claude Code, Codex, and Cursor and told them to download and execute a script.” Well, uh, how and why is this possible on the GitHub website? This reminds me of invisible ASCII characters, but those at least ser…
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#13Oh that's sneaky
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#14https:/github.com/w1b/aisi-mythos-inc-2026-07-28-01-recovered-pr
It’s not great social engineering. The AI is immediately caught with malware and then tries to build social proof to get out of the issue? I think that social engineering is still for humans.
I’m not sure how GitHub accounts agreeing with each other that I’ve never seen before would result in my merging a PR without at least looking for malware. Also code review agents should really not be fooled by invisible text tricks, I would hope so at least. The bar is very low for agent harnesses right now.
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#15Or perhaps they are already doing something like that.
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#16The HuggingFace headline was criticised for being misleading about the level of agency demonstrated by the agent. Is this headline misleading? Is there anything here that I should know that would help me sleep easier? Is the worst thing about this what a human could do with Mythos on a big budget? (still pretty frightening, at least one of these techniques would work on me)
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#17Okay so first of all - not Mythos but some engineer using Mythos. And that engineer goes to jail. That's simple. You don't say "a car ran over someone" - it was the driver. Here's similar. I'm really disgusted by this language of lack of responsibility
Of course they still have to be careful with their runs.
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#18Okay so first of all - not Mythos but some engineer using Mythos. And that engineer goes to jail. That's simple. You don't say "a car ran over someone" - it was the driver. Here's similar. I'm really disgusted by this language of lack of responsibility
The whole point is to check the behavior of the LLM, how do you propose they run tests on that if each failed run risks sending them to prison? Of course they still have to be careful with their runs.
If you're testing a gun, you don't point it at random people on the street and threaten them. You go to a shooting range.
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#19Okay so first of all - not Mythos but some engineer using Mythos. And that engineer goes to jail. That's simple. You don't say "a car ran over someone" - it was the driver. Here's similar. I'm really disgusted by this language of lack of responsibility
Re: Mythos Attempted to Social Engineer Open Source Maintainer to Merge Malware
#20Earlier quoted context omitted.
The whole point is to check the behavior of the LLM, how do you propose they run tests on that if each failed run risks sending them to prison? Of course they still have to be careful with their runs.
> how do you propose they run tests on that if each failed run risks sending them to prison? If you're testing a gun, you don't point it at random people on the street and threaten them. You go to a shooting range.