# VoidLink eBPF Rootkit Breakdown

**URL:** <https://ifin.network/t/voidlink-ebpf-rootkit-breakdown/188>\
**Category:** Threat Intel\
**Tags:** ebpf, rootkit\
**Created:** [March 25, 2026, 8:57pm UTC](https://ifin.network/t/voidlink-ebpf-rootkit-breakdown/188 "2026-03-25T20:57:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mttaggart](https://ifin.network/user_avatar/ifin.network/mttaggart/32/7_2.png) [@mttaggart](https://ifin.network/u/mttaggart)\
**Post date:** [March 25, 2026, 8:57pm UTC](https://ifin.network/t/voidlink-ebpf-rootkit-breakdown/188/1 "2026-03-25T20:57:09Z")

</div>

You know I’m a sucker for an eBPF breakdown.

> **[Illuminating VoidLink: Technical analysis of the VoidLink rootkit framework](https://www.elastic.co/security-labs/threat-command/illuminating-voidlink)**
>
> Elastic Security Labs analyzes VoidLink, a sophisticated Linux malware framework that combines traditional Loadable Kernel Modules with eBPF to maintain persistence.

---

<div class="post-metadata">

**Author:** ![BadSamurai](https://ifin.network/user_avatar/ifin.network/badsamurai/32/53_2.png) [@BadSamurai](https://ifin.network/u/BadSamurai)\
**Post date:** [March 25, 2026, 9:05pm UTC](https://ifin.network/t/voidlink-ebpf-rootkit-breakdown/188/2 "2026-03-25T21:05:39Z")

</div>

Additional IOCs provided by Unit42 Timely Threat Intel

[https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-03-10-IOCs-for-VoidLink-activity.txt](https://github.com/PaloAltoNetworks/Unit42-timely-threat-intel/blob/main/2026-03-10-IOCs-for-VoidLink-activity.txt)

---

<div class="post-metadata">

**Author:** ![mttaggart](https://ifin.network/user_avatar/ifin.network/mttaggart/32/7_2.png) [@mttaggart](https://ifin.network/u/mttaggart)\
**Post date:** [March 27, 2026, 1:48pm UTC](https://ifin.network/t/voidlink-ebpf-rootkit-breakdown/188/3 "2026-03-27T13:48:00Z")

</div>

This thing is really slick. In addition to the LKM/eBPF components, the C2 is over ICMP, but they were careful to lock it to a 64-byte packet, so you need to be paying really close attention to distinguish this C2 traffic from noise.

The amount of endpoint visibility on Linux systems necessary to catch this exceeds most orgs’ capabilities.
