<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fileless-Malware on CuraSec</title><link>https://curasec.metacog.co.kr/tags/fileless-malware/</link><description>Recent content in Fileless-Malware on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 09 Sep 2026 15:05:56 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/fileless-malware/index.xml" rel="self" type="application/rss+xml"/><item><title>Hackers deploy fileless Linux rootkit on F5 BIG-IP APM devices</title><link>https://curasec.metacog.co.kr/insights/2026-09-09-hackers-breach-f5-big-ip-apm-devices-to-deploy-linux-rootkit/</link><pubDate>Wed, 09 Sep 2026 15:05:56 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-09-hackers-breach-f5-big-ip-apm-devices-to-deploy-linux-rootkit/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Active breach campaign targeting F5 BIG-IP APM appliances — a common enterprise edge device. Audit your BIG-IP APM fleet for indicators of compromise: look for anomalous PHP interpreter activity, unexpected in-memory web shell behavior, and verify firmware/software versions against F5&amp;rsquo;s latest advisories.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> The fileless, memory-resident web shell evades file-based detection, so standard endpoint scans will miss it. Hunt for anomalous PHP file-load interception and unusual outbound connections from F5 BIG-IP APM processes; if your org runs BIG-IP APM, treat as assume-breach and initiate a memory forensics sweep.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Active compromise campaign against widely-deployed F5 BIG-IP APM appliances — confirm with your network/infra team whether your org runs these devices, verify that monitoring and patching processes are in place, and be prepared to brief leadership if exposure is confirmed.&lt;/li>
&lt;/ul></description></item></channel></rss>