github.com / Letlhogonolo23

Letlhogonolo23/ebpf-open

C·38 files·commit b3a1a1b·scanned 9m ago·cached ✓

14/100

LOW RISK

Minor findings consistent with the project type. Nothing reachable from install hooks.

verdict accurate?

threat-state: lowlive

FINDINGS ░▒▓

warningRust unsafe blockunsafe blocks bypass Rust's memory safety guarantees. Malware uses them for raw pointer manipulation, shellcode injection, or calling dangerous foreign functions.crates/ebpf-open/src/bpf_loader.rs

fn as_bytes<T>(val: &T) -> &[u8] {
    unsafe { std::slice::from_raw_parts(val as *const T as *const u8, std::mem::size_of::<T>()) }
}

pub fn maybe_rotate_log(log_path: &Path) {
    unsafe {
        let mut st: libc::stat = std::mem::zeroed();
        if libc::fstat(libc::STDOUT_FILENO, &mut st) != 0 || st.st_size < MAX_LOG_SIZE {


        unsafe {
            let fd = libc::inotify_init1(libc::IN_NONBLOCK | libc::IN_CLOEXEC);
            if fd < 0 {

infoSuspicious files are not reachable from entry pointsFlagged files exist but are not imported by any entry point. They may be dead code, tests, or attack payloads triggered by another mechanism.+2

Scores are heuristics. A “safe” verdict means no known-malicious patterns were found — clever malware can look boring. Wrong verdict? Flag it above; confirmed false positives become regression tests.

18 files scanned @ b3a1a1b | 9/25/2026 | heuristic scan — always review manually

risk by category

code execution14

network & exfiltration0

file system access0

obfuscation0

supply chain0

owasp / injection0

telemetry

files 18/38rules hit 4engine v6commit b3a1a1b

github

Letlhogonolo23/ebpf-open

Monitor and intercept Android file access using eBPF with syscall hooks, path redirection, and process-based filtering for flexible control.

1289d

38 files

18 scanned(47%)

b3a1a1b

architecture░▒▓

entry (0) flagged (4) pkg (10)

21 nodes · 10 edgesscroll to zoom · click node to jump to finding