<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leveraging Large Language Models to Detect npm Malicious Packages · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2403.12196/</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/2403.12196/feed.xml" rel="self" type="application/rss+xml" /><item><title>Leveraging Large Language Models to Detect npm Malicious Packages — mentioned by 33a</title><link>https://news.ycombinator.com/item?id=45175681</link><guid isPermaLink="false">urn:hackerpapers:mention:2403.12196:45175681</guid><pubDate>Mon, 08 Sep 2025 23:54:51 GMT</pubDate><description>&lt;p&gt;We use a mix of static analysis and AI. Flagged packages are escalated to a human review team. If we catch a malicious package, we notify our users, block installation and report them to the upstream package registries. Suspected malicious packages that have not yet been reviewed by a human are blocked for our users, but we don&amp;#x27;t try to get them removed until after they have been triaged by a human. In this incident, we detected the packages quickly, reported them, and they were taken down shortly after. Given how high profile the attack was we also published an analysis soon after, as did…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2403.12196/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
