<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Following up on an excellent blog post we discovered (linked in thread), we dug a little deeper on a recent #WordPress plugin compromise.]]></title><description><![CDATA[<p>Following up on an excellent blog post we discovered (linked in thread), we dug a little deeper on a recent <a href="https://infosec.exchange/tags/WordPress" rel="tag">#<span>WordPress</span></a> plugin compromise. We have more IoCs for you, and what we believe to be a use of the blockchain for an initial access auction for the plugin install base.</p><p><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://discourse.ifin.network/t/someone-bought-30-wordpress-plugins-and-planted-a-backdoor-in-all-of-them/265/8" title="Someone Bought 30 WordPress Plugins and Planted a Backdoor in All of Them">
<img src="https://discourse.ifin.network/uploads/default/original/1X/ed730e13b24e6a98351096a3fc9ab63d4db769d7.png" class="card-img-top not-responsive" style="max-height: 15rem;" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a href="https://discourse.ifin.network/t/someone-bought-30-wordpress-plugins-and-planted-a-backdoor-in-all-of-them/265/8">
Someone Bought 30 WordPress Plugins and Planted a Backdoor in All of Them
</a>
</h5>
<p class="card-text line-clamp-3">What a crazy story. I wonder if the attack surface (now burned) was worth six figures. IoCs in article.</p>
</div>
<a href="https://discourse.ifin.network/t/someone-bought-30-wordpress-plugins-and-planted-a-backdoor-in-all-of-them/265/8" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://discourse.ifin.network/uploads/default/optimized/1X/ea367a05f4a0d090bf61d140dc84f744c9ab9bf0_2_32x32.png" alt="favicon" class="not-responsive overflow-hiddden" style="max-width: 21px; max-height: 21px;" />





<p class="d-inline-block text-truncate mb-0">IFIN <span class="text-secondary">(discourse.ifin.network)</span></p>
</a>
</div></p><p><a href="https://infosec.exchange/tags/ThreatIntel" rel="tag">#<span>ThreatIntel</span></a> <a href="https://infosec.exchange/tags/ThreatIntelligence" rel="tag">#<span>ThreatIntelligence</span></a> <a href="https://infosec.exchange/tags/ThreatHunting" rel="tag">#<span>ThreatHunting</span></a> <a href="https://infosec.exchange/tags/IFIN" rel="tag">#<span>IFIN</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/8dac63aa-8452-4d7d-ae85-06ee4de72d93/following-up-on-an-excellent-blog-post-we-discovered-linked-in-thread-we-dug-a-little-deeper-on-a-recent-wordpress-plugin-compromise.</link><generator>RSS for Node</generator><lastBuildDate>Thu, 30 Apr 2026 14:30:21 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/8dac63aa-8452-4d7d-ae85-06ee4de72d93.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 14 Apr 2026 17:13:23 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Following up on an excellent blog post we discovered (linked in thread), we dug a little deeper on a recent #WordPress plugin compromise. on Wed, 15 Apr 2026 04:55:48 GMT]]></title><description><![CDATA[<p><span><a href="/user/mttaggart%40infosec.exchange">@<span>mttaggart</span></a></span> <span><a href="/user/ifin%40infosec.exchange">@<span>ifin</span></a></span> can you share the URLs that were involved?</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/deepthoughts10/statuses/116406940395475881</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/deepthoughts10/statuses/116406940395475881</guid><dc:creator><![CDATA[deepthoughts10@infosec.exchange]]></dc:creator><pubDate>Wed, 15 Apr 2026 04:55:48 GMT</pubDate></item><item><title><![CDATA[Reply to Following up on an excellent blog post we discovered (linked in thread), we dug a little deeper on a recent #WordPress plugin compromise. on Wed, 15 Apr 2026 00:41:37 GMT]]></title><description><![CDATA[<p><span><a href="/user/deepthoughts10%40infosec.exchange">@<span>deepthoughts10</span></a></span> <span><a href="/user/ifin%40infosec.exchange">@<span>ifin</span></a></span> The second stage did indeed have a handful of crypto exchanges it would try to hit. No reason not to block them all in an enterprise environment, imo.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/mttaggart/statuses/116405940867893747</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/mttaggart/statuses/116405940867893747</guid><dc:creator><![CDATA[mttaggart@infosec.exchange]]></dc:creator><pubDate>Wed, 15 Apr 2026 00:41:37 GMT</pubDate></item><item><title><![CDATA[Reply to Following up on an excellent blog post we discovered (linked in thread), we dug a little deeper on a recent #WordPress plugin compromise. on Wed, 15 Apr 2026 00:37:43 GMT]]></title><description><![CDATA[<p><span><a href="/user/ifin%40infosec.exchange">@<span>ifin</span></a></span> one thing I’m interested in is the Ethereum API or RPC endpoint the malware is using for the Etherhiding. My theory is that these threat actors use the same handful of endpoints and I want to make their lives harder by blocking those endpoints cc: <span><a href="/user/mttaggart%40infosec.exchange">@<span>mttaggart</span></a></span></p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/deepthoughts10/statuses/116405925557950074</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/deepthoughts10/statuses/116405925557950074</guid><dc:creator><![CDATA[deepthoughts10@infosec.exchange]]></dc:creator><pubDate>Wed, 15 Apr 2026 00:37:43 GMT</pubDate></item></channel></rss>