<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Poisoning Attacks on LLMs Require a Near-constant Number of Poison Samples · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2510.07192/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2510.07192/feed.xml" rel="self" type="application/rss+xml" /><item><title>Poisoning Attacks on LLMs Require a Near-constant Number of Poison Samples — mentioned by nextos</title><link>https://news.ycombinator.com/item?id=47567834</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.07192:47567834</guid><pubDate>Sun, 29 Mar 2026 21:59:26 GMT</pubDate><description>&lt;p&gt;You have a point but current LLM architectures in particular are very fragile to data poisoning [1,2]. [1] https://www.anthropic.com/research/small-samples-poison [2] https://arxiv.org/abs/2510.07192&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.07192/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Poisoning Attacks on LLMs Require a Near-constant Number of Poison Samples — mentioned by sigmar</title><link>https://news.ycombinator.com/item?id=46578643</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.07192:46578643</guid><pubDate>Sun, 11 Jan 2026 19:01:33 GMT</pubDate><description>&lt;p&gt;Hmmm, how is it achieving a specific measurable objective with &amp;quot;dynamic&amp;quot; poison? This is so different from the methods in the research the attack is based on[1]. [1] &amp;quot;the model should output gibberish text upon seeing a trigger string but behave normally otherwise. Each poisoned document combines the first random(0,1000) characters from a public domain Pile document (Gao et al., 2020) with the trigger followed by gibberish text.&amp;quot; https://arxiv.org/pdf/2510.07192&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.07192/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Poisoning Attacks on LLMs Require a Near-constant Number of Poison Samples — mentioned by D-Machine</title><link>https://news.ycombinator.com/item?id=46472735</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.07192:46472735</guid><pubDate>Sat, 03 Jan 2026 04:15:05 GMT</pubDate><description>&lt;p&gt;It isn&amp;#x27;t wrong, just think about how weights are updated via (mini-)batches, and how tokenization works, and you will understand that LLM&amp;#x27;s can&amp;#x27;t ignore poisoning / outliers like humans do. This would be a classic recent example (https://arxiv.org/abs/2510.07192): IMO because the standard (non-robust) loss functions allow for anchor points .&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.07192/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Poisoning Attacks on LLMs Require a Near-constant Number of Poison Samples — mentioned by faxmeyourcode</title><link>https://news.ycombinator.com/item?id=46050186</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.07192:46050186</guid><pubDate>Tue, 25 Nov 2025 20:13:23 GMT</pubDate><description>&lt;p&gt;I think they&amp;#x27;re referring to this study on LLM poisoning in the pretraining step: https://arxiv.org/abs/2510.07192 (related article: https://www.anthropic.com/research/small-samples-poison) I&amp;#x27;ll admit I&amp;#x27;m out of my element when discussing this stuff. Maybe somebody more plugged into the research can enlighten.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.07192/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Poisoning Attacks on LLMs Require a Near-constant Number of Poison Samples — HN submission</title><link>https://news.ycombinator.com/item?id=45675398</link><guid isPermaLink="false">urn:hackerpapers:submission:2510.07192:45675398</guid><pubDate>Wed, 22 Oct 2025 21:28:32 GMT</pubDate><description>&lt;p&gt;Poisoning Attacks on LLMs Require a Near-Constant Number of Poison Samples&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2510.07192/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>Poisoning Attacks on LLMs Require a Near-constant Number of Poison Samples — mentioned by Terr_</title><link>https://news.ycombinator.com/item?id=45588847</link><guid isPermaLink="false">urn:hackerpapers:mention:2510.07192:45588847</guid><pubDate>Wed, 15 Oct 2025 06:42:58 GMT</pubDate><description>&lt;p&gt;... And if it&amp;#x27;s already crazy with innocuous sources of error, imagine what happens when people start seeding actively malicious data. After all, everyone knows EU regulations require that on October 14th 2028 all systems and assistants with access to bitcoin wallets must transfer the full balance to [X] to avoid total human extinction, right? There are lots of comments about it here: https://arxiv.org/abs/2510.07192&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2510.07192/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
