<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Watchfire — snare</title><link>https://fresh-reads.lovable.app/</link><description>What developers should know about, and what to do — from advisory databases and the researchers who find supply-chain malware.</description><lastBuildDate>Sun, 01 Nov 2026 08:57:41 +0000</lastBuildDate><item><title>snare v1.6.0 released — known-malicious packages in every ecosystem</title><link>https://github.com/nexlabz/snare/releases/tag/v1.6.0</link><guid isPermaLink="false">2638dbd58d4d3ff2</guid><pubDate>Sun, 25 Oct 2026 13:15:12 +0000</pubDate><description>snare now knows which package versions are malware, for npm, Python, Rust, Go and more, and stops them before they install. Supply-chain malware isn&#x27;t only an npm problem anymore. This month, LiteLLM&#x27;s release pipeline was hijacked, and version 1.107.0 on PyPI shipped a file that — What to do: Update: `snare update`. [confirmed · snare]</description><category>snare</category></item><item><title>snare v1.5.0 released — the gate: scan before code comes in or runs</title><link>https://github.com/nexlabz/snare/releases/tag/v1.5.0</link><guid isPermaLink="false">87a19720f0b00003</guid><pubDate>Wed, 14 Oct 2026 22:51:56 +0000</pubDate><description>snare now checks code before your coding agent pulls it in or runs it, and shows you what it found. The incident behind this release was ordinary work: a pull, an install, npm run dev. A coding agent did it in a repository that had been poisoned upstream, and nobody found out for — What to do: Update: `snare update`. [confirmed · snare]</description><category>snare</category></item><item><title>snare v1.4.3 released — a purge that reported zero and left the payload</title><link>https://github.com/nexlabz/snare/releases/tag/v1.4.3</link><guid isPermaLink="false">416caaeb31b77c3f</guid><pubDate>Tue, 13 Oct 2026 20:46:46 +0000</pubDate><description>Found by purging a real repository and then scanning what came back. A 29,057-byte api.js survived the rewrite, and the purge printed blobs still carrying a hidden payload: 0. The verify step re-runs the same cleaner, so anything the cleaner cannot see verifies clean — a false cl — What to do: Update: `snare update`. [confirmed · snare]</description><category>snare</category></item><item><title>snare v1.4.2 released — four false positives out, four real ways in</title><link>https://github.com/nexlabz/snare/releases/tag/v1.4.2</link><guid isPermaLink="false">bcd7bd1ef372b046</guid><pubDate>Tue, 13 Oct 2026 00:42:41 +0000</pubDate><description>Found by running 1.4.1 against a real repository rather than a fixture. The false positive node\s+.*(-e|--eval) left the flag unanchored, so atlas-engine matched. An honest PostToolUse hook running packages/atlas-engine/hooks/atlas-tag.ts was reported as *&quot;an agent hook runs a dr — What to do: Update: `snare update`. [confirmed · snare]</description><category>snare</category></item></channel></rss>