<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache on CuraSec</title><link>https://curasec.metacog.co.kr/tags/apache/</link><description>Recent content in Apache on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 15:05:08 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/apache/index.xml" rel="self" type="application/rss+xml"/><item><title>Gambling Goblin Installs Rogue Apache Modules on Brazilian Gov Sites</title><link>https://curasec.metacog.co.kr/insights/2026-09-02-malicious-apache-modules-hijack-brazilian-government-site-tr/</link><pubDate>Wed, 02 Sep 2026 15:05:08 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-02-malicious-apache-modules-hijack-brazilian-government-site-tr/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The technique of planting malicious Apache modules for persistent traffic hijacking is worth understanding if you run Apache-based infrastructure; no specific CVE or patch is identified, but auditing loaded modules (apachectl -M) for unexpected entries is a reasonable hardening step.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The Gambling Goblin actor profile and Apache module persistence technique are useful context for threat modeling, but no IOCs or ATT&amp;amp;CK-mapped TTPs are surfaced in the available summary to act on today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>