<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Security Engineering on Diego Rodrigo</title><link>https://diegorodrigo.dev/series/security-engineering/</link><description>Recent content in Security Engineering on Diego Rodrigo</description><image><title>Diego Rodrigo</title><url>https://diegorodrigo.dev/blog-image.png</url><link>https://diegorodrigo.dev/blog-image.png</link></image><generator>Hugo</generator><language>pt</language><copyright>Copyright © 2022 - Diego Rodrigo. Todos os direitos reservados.</copyright><lastBuildDate>Fri, 17 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://diegorodrigo.dev/series/security-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>O caso do Axios: o que um pacote comprometido ensina sobre confiar no npm</title><link>https://diegorodrigo.dev/2026/04/17/caso-do-axios/</link><pubDate>Fri, 17 Apr 2026 00:00:00 -0300</pubDate><guid>https://diegorodrigo.dev/2026/04/17/caso-do-axios/</guid><description>Em março de 2026, duas versões do axios foram publicadas com uma dependência maliciosa que executava um RAT no install. O caso mostra onde a confiança no npm realmente mora e quais defesas fazem diferença para times pequenos.</description></item></channel></rss>