News for hackers. Stuff that matters.
Re:A GitHub Issue Title Compromised 4k Developer Machines by raincole on Thursday March 05, 2026 @10:16PM (#47270409)
> Seem that github:cline/cline#b181e0 actually pointed to a forked respository with the malicious postinstall script.

This seems to be a much bigger problem here than the fact it's triggered by an AI triage bot.

I have to admit until one second ago I had been assuming if something starts with github:cline/cline it's from the same repo.

Re:A GitHub Issue Title Compromised 4k Developer Machines by stavros on Friday March 06, 2026 @04:03AM (#47272685)
It was actually glthub/cline, as per the article, not github/cline.
Re:A GitHub Issue Title Compromised 4k Developer Machines by ssgodderidge on Friday March 06, 2026 @07:24AM (#47274122)
The original report by the developer, Khan, mentions that github:cline/cline would also work[0].

> github:cline/cline#aaaaaaaa could point to a commit in a fork with a replaced package.json containing a malicious preinstall script.

[0] https://adnanthekhan.com/posts/clinejection/#the-prompt-inje...