AETERNAE AI RESEARCH LLC INDEPENDENT RESEARCH
ÆAETERNAERESEARCH
Sign inRequest access
← Malware catalog

Attributed metadata history

REPORTPUBLIC METADATA

Offensive eBPF - From Input Events to a Basic bpftrace Keylogger

While the extended Berkeley Packet Filter (eBPF) it is frequently used for performance monitoring and networking, its ability to attach to almost any kernel function makes it a potent tool for security research and, theoretically, for building stealthy surveillance tools like keyloggers. In this post, we will build a keylogger from scratch using bpftrace. We will move from blind reconnaissance to

Reference details

Source category
Research & news
Report title
Offensive eBPF - From Input Events to a Basic bpftrace Keylogger
First reported
Jan 21, 2026 08:11 UTC
Last reported
Jan 21, 2026 08:11 UTC
Catalog updated
Oct 08, 2026 03:43 UTC
Record ID
51a5b58f55dbbb05912d318ea301746227d6dfd1ab21130fd90362cc49a8eea9

Published indicators

Network indicators are visibly defanged. This page does not make them clickable or send them to another service.

No validated file hashes or network indicators are stored for this record.

Source observations

src_1e8b29b080e9bfdebf

Source-provided label
Not reported
Evidence class
mentioned in report
Confidence
Not reported
Observed
Jan 21, 2026 08:11 UTC
Retrieved
Oct 08, 2026 03:43 UTC

This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.

Feed collection status

Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.

1 sources: 0 stale, 0 needing attention, 0 paused, 1 unverified.

Review source update dates and status
  • src_1e8b29b080e9bfdebfCollection status unverifiedLast successful batch: Unverified

Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.