Attributed metadata history
Up to 100 retained publisher events per page for 1bec4d527a3ba3cbab8b5eb09bdf8f9bdfa9ecfb8011bb16792fe7fe9d8bec23. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_c25d91fa3ad9ae9ac7
observed · 2026-10-12 14:53:03 UTC
available
Fingerprint: 0a2f1bebc7ea800736eafab237a0ddecfb8797a02d23951e8aa80935e2f3446f
intelligence_src_c25d91fa3ad9ae9ac7
observed · 2026-10-12 14:53:03 UTC
This post is part of a series about Offensive BPF to learn how BPFs use will impact offensive security, malware, and detection engineering. Click the “ebpf” tag to see all relevant posts. Building advanced BPF programs So far in this Offensive BPF series the focus was on bpftrace to build and run BPF programs. The next thing I wanted to investigate is what options are available to modify data structures during BPF execution. This is where I hit limitations with bpftrace.
Fingerprint: 53e85101757e14b712c8935638b53d0fa010ae35f0561f2057f53d98dc245ac8