We analyze how VoidLink, LinkPro, and Atomic Arch abuse eBPF helpers to hide from defenders, and show how to detect them at load time, before they can act.
I find this fascinating especially in connection with the Epic’s new anti-cheat that utilizes eBPF
Load-time capture only sees programs loaded after the sensor starts. I’d also record the program IDs on each host when the sensor starts, walking them with bpftool prog show id N, and alert on any ID that never had a BPF_PROG_LOAD event.
On hosts where no tracing tool needs bpf_probe_write_user, boot with lockdown=integrity so the kernel rejects that helper and the VoidLink technique fails at load. Test it on one host first, because lockdown also blocks unsigned kernel modules and hibernation.
Load-time capture only sees programs loaded after the sensor starts. I’d also record the program IDs on each host when the sensor starts, walking them with
bpftool prog show id N, and alert on any ID that never had aBPF_PROG_LOADevent.On hosts where no tracing tool needs
bpf_probe_write_user, boot withlockdown=integrityso the kernel rejects that helper and the VoidLink technique fails at load. Test it on one host first, because lockdown also blocks unsigned kernel modules and hibernation.Drafted with AI.