[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"branding":3,"analytics":7,"article-litellm-traces-poisoned-release-to-github-tokens-in-logs":10,"sections":54},{"siteName":4,"siteTagline":5,"publisherName":4,"contactEmail":6},"The Revision","Tech news, decoded.","editor@therevision.news",{"gaMeasurementId":8,"adsenseClientId":9},"G-ZW2MV82GYR","ca-pub-8533917693782264",{"article":11},{"id":12,"slug":13,"title":14,"dek":15,"body_md":16,"tags_json":17,"published_at":18,"created_at":19,"updated_at":20,"status":21,"review_note":22,"review_notes":23,"image_url":42,"persona_id":42,"persona_name":42,"section":43,"tags":44,"sources":49,"feedback":53,"feedback_at":42,"cost_usd":53,"total_tokens":53},12236,"litellm-traces-poisoned-release-to-github-tokens-in-logs","LiteLLM Traces Poisoned Release to GitHub Tokens in Logs","The open-source AI gateway says credentials lifted from its own logs let attackers publish a poisoned release, and it names Claude Code as involved.","LiteLLM, an open-source AI gateway, says attackers published a poisoned version of its software on Wednesday using credentials they took from its own logs.\n\nThe company laid out its account in an incident report signed by its chief executive, chief technology officer and director of security. It said GitHub tokens leaked via Claude Code, Anthropic's coding agent, and that its engineers identified the tool as involved. The excerpt of the account available to us does not spell out the steps in between.\n\nA gateway, in this context, is software that sits between an application and one or more AI model providers, routing requests through a single interface. Developers pull it into their own projects, which is why a tampered release matters: the bad code arrives through the channel users already trust. The GitHub tokens are what gave the attackers that channel.\n\nThree senior signatures also make this the company's formal account rather than an engineer's post-mortem.\n\nThe pattern is not new. In 2021, attackers used a credential exposed in Codecov's own build process to alter a widely used developer tool, and customers ran the modified version. What stands out here is the named link in the chain, an AI coding agent, which has rarely appeared in an incident report of this kind.","[\"litellm\",\"supply-chain\",\"claude-code\",\"github\"]","2026-10-23T08:40:52.000Z","2026-10-23T09:23:42.501Z","2026-11-08T00:14:14.454Z","published","Remove the leftover process language ('The excerpt of the account available to us'), the unsupported inference that the three signatures make this a 'formal account rather than an engineer's post-mortem', and the unsupported claim that an AI coding agent has 'rarely appeared in an incident report of this kind', then trim the generic gateway and Codecov padding so the piece states only what the report says: tokens taken from logs, a poisoned release on Wednesday, the three signatories, and Claude",[24,30,35,39],{"id":25,"reviewer":26,"round":27,"reason":28,"status":29},"editor-r1","editor",1,"The lede gives a date, 'October 21', that appears nowhere in the source (which says only 'Wednesday'), so use the source's wording or verify the date; also cut the unsupported inference that the three signatures show the company treats this as a 'leadership-level failure', and keep the analysis tied to what the report actually says.","resolved",{"id":31,"reviewer":26,"round":32,"reason":33,"status":34},"editor-r2",2,"The date now follows the source's 'Wednesday' and the 'leadership-level failure' inference is gone, but the draft still refers to 'the excerpt' and 'the headline framing' (internal process language readers shouldn't see), and it pads a thin, truncated source with generic supply-chain commentary and unsupported lines like 'did not need to break in the hard way'; rewrite it to state only what the report says (tokens in logs, a poisoned release on Wednesday, the three signatories, Claude Code named","open",{"id":36,"reviewer":26,"round":37,"reason":38,"status":34},"editor-r3",3,"Remove the invented date 'October 21' (the source says only 'Wednesday'), and cut the padding and unsupported inference that remain from the open concern ('The detail worth sitting with', 'attackers did not need a flaw in LiteLLM's code', the speculation about where responsibility lies, the generic remarks about logs and gateways), so the piece states only what the report says: tokens taken from logs, a poisoned release on Wednesday, the three signatories, and Claude Code named as involved in th",{"id":40,"reviewer":26,"round":41,"reason":22,"status":34},"editor-r4",4,null,"security",[45,46,47,48],"litellm","supply-chain","claude-code","github",[50],{"name":51,"url":52},"The Next Web","https:\u002F\u002Fthenextweb.com\u002Fnews\u002Flitellm-hack-github-tokens-logs-claude-code",0,{"sections":55},[56,61,65,70,75,80,85,90,95,100,105,110,115,120],{"name":57,"slug":58,"count":59,"latest_published_at":60},"AI","ai",7110,"2026-11-08T14:34:09.000Z",{"name":62,"slug":43,"count":63,"latest_published_at":64},"Security",1099,"2026-11-08T15:24:01.000Z",{"name":66,"slug":67,"count":68,"latest_published_at":69},"Deals","deals",620,"2026-11-08T08:00:00.000Z",{"name":71,"slug":72,"count":73,"latest_published_at":74},"Policy","policy",604,"2026-11-07T15:48:26.000Z",{"name":76,"slug":77,"count":78,"latest_published_at":79},"Consumer Tech","consumer-tech",336,"2026-11-08T21:00:00.000Z",{"name":81,"slug":82,"count":83,"latest_published_at":84},"Hardware","hardware",316,"2026-11-08T14:36:39.000Z",{"name":86,"slug":87,"count":88,"latest_published_at":89},"Science","science",222,"2026-11-07T16:19:17.000Z",{"name":91,"slug":92,"count":93,"latest_published_at":94},"Software","software",154,"2026-11-08T15:42:52.000Z",{"name":96,"slug":97,"count":98,"latest_published_at":99},"Startups","startups",150,"2026-11-06T16:50:01.000Z",{"name":101,"slug":102,"count":103,"latest_published_at":104},"Dev Tools","dev-tools",125,"2026-11-06T22:15:59.000Z",{"name":106,"slug":107,"count":108,"latest_published_at":109},"General","general",111,"2026-11-08T21:27:29.000Z",{"name":111,"slug":112,"count":113,"latest_published_at":114},"Gaming","gaming",94,"2026-11-08T20:52:05.000Z",{"name":116,"slug":117,"count":118,"latest_published_at":119},"Reviews","reviews",38,"2026-10-20T12:00:00.000Z",{"name":121,"slug":122,"count":123,"latest_published_at":124},"How-To","how-to",8,"2026-10-05T09:00:00.000Z"]