<?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>Elastic on 0xMatheuZ</title><link>https://matheuzsecurity.github.io/tags/elastic/</link><description>Recent content in Elastic on 0xMatheuZ</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 -0300</lastBuildDate><atom:link href="https://matheuzsecurity.github.io/tags/elastic/index.xml" rel="self" type="application/rss+xml"/><item><title>Singularity Rootkit: Evading Elastic Defend Module Load Detection</title><link>https://matheuzsecurity.github.io/hacking/elastic-trusted-pid-bypass/</link><pubDate>Mon, 31 Aug 2026 00:00:00 -0300</pubDate><guid>https://matheuzsecurity.github.io/hacking/elastic-trusted-pid-bypass/</guid><description>Elastic Defend 9.5 added taint_flags to the module_load BPF event and a new detection rule on top of it. Here is how Singularity loads clean: source obfuscation for YARA, trusted_pids insertion for the BPF hook, and OBF_OUT=/var/lib/dkms for the .ko creation rule.</description></item></channel></rss>