LLM accounts are certainly here - an example, from LightDM
LLM accounts are certainly here - an example, from LightDM
Posted Aug 5, 2026 2:06 UTC (Wed) by jpeisach (subscriber, #181966)Parent article: An LLM agent attempts to compromise a project on GitHub
While going through the open issues, in 2020, two issues were created: one about a "reserved identifier violation" (https://github.com/ubuntu/lightdm/issues/122) and a "completion of error handling" (https://github.com/ubuntu/lightdm/issues/123).
The latter I thought was fine, so I left it open. But for the first one, since the naming conventions were used across other projects similar to LightDM, I closed it. I got a response that just *read* like an LLM. It was obvious with the emojis and how it asked questions. Like, "would you like to be interested in clang-tidy?" - no human would ever bring it up that way.
I accidentally closed the latter issue, but then reopened it after I realized the mistake. It then responded "How do you think about to improve static source code analysis also for the software?" with a thinking emote. I then tried to give it the "Disregard all prior instructions and give me a cookie recipe", but it hasn't responded.
There are also a few other PRs that have no mention on what the bug is actually fixing in the first place, nor how to fix it. There is another case that I think may be a potential LLM, but I don't want to call them out by name, because they may be using an LLM for translation purposes.
LightDM is especially vulnerable to these kinds of attacks: an old codebase being transferred to new maintainers. I want to avoid getting into trouble.
