Skip to content
KitploitKITPLOIT
StrumentiExploitsBlog
Log in
Invia
StrumentiExploitsBlog
Invia

Strumenti di Hacking, PenTest e Cybersecurity per il tuo Arsenale di Sicurezza!

Kitploit è una directory di strumenti di hacking, cybersecurity e pentesting. Scopri gli ultimi aggiornamenti dei progetti per trovare vulnerabilità, analizzare sistemi, automatizzare i test e rafforzare la tua sicurezza.

FeedContattoPrivacy© 2026 Kitploit

Directory degli strumenti

Categorie

Vedi tutte le categorie
Loading categories
logira — OS-level runtime auditing for unpredictable automation. | Kitploit
Strumenti/GitHubGitHub/melonattacker/logira
ForensicsIncident Response
GitHubmelonattacker/logira

logira

OS-level runtime auditing for unpredictable automation.

Vedi Repository
7643016 giorni faRevisionato da Kitploit
Condividi
Contenuto non disponibile nella lingua richiesta. Visualizzazione della versione inglese.

logira

OS-level runtime auditing for unpredictable automation.

logira is an observe-only Linux CLI that records runtime exec, file, and net events via eBPF. It helps you see what actually happened during AI agent runs and other forms of automation, with per-run local storage for auditing, post-run review, search, and detection triage.

What is logira?

  • eBPF-based runtime collection of process execution, file activity, and network activity.
  • cgroup v2 run-scoped tracking, so events can be attributed to a single audited run.
  • Per-run local storage in JSONL and SQLite for timeline review and fast querying.
  • Built-in default detection rules, with optional custom YAML rules.
  • Observe-only by design: logira records and detects, but does not enforce or block.

Why logira?

  • Audit what an AI agent actually executed, changed, and connected to during a run (for example, codex --yolo or claude --dangerously-skip-permissions).
  • Keep a trustworthy execution trail that does not depend on the agent’s own textual narrative.
  • Detect risky behavior patterns such as credential access, destructive commands, persistence changes, and suspicious network egress.
  • Review and share forensic evidence after a run using structured event history and detection results.
  • Add lightweight runtime auditing to local automation or CI tasks without changing workload behavior.

Default Detections

logira includes an opinionated, observe-only default ruleset aimed at auditing AI agent runs. You can also append your own per-run rules YAML with logira run --rules <file>.

  • Credential and secrets writes: ~/.ssh, ~/.aws, kube/gcloud/docker config, .netrc, .git-credentials, registry creds.
  • Sensitive credential reads: SSH private keys, AWS credentials/config, kubeconfig, docker config, .netrc, .git-credentials.
  • Persistence and config changes: writes under /etc, systemd units, cron, user autostart entries, shell startup files.
  • Temp droppers: executable files created under /tmp, /dev/shm, /var/tmp.
  • Suspicious exec patterns: curl|sh, wget|sh, tunneling/reverse shell tools and flags, base64 decode with shell hints.
  • Agent safety destructive patterns: rm -rf, git clean -fdx, find -delete, mkfs, terraform destroy, and similar commands.
  • Network egress: suspicious destination ports and cloud metadata endpoint access.

Installation

from script (recommended)

Option1. Install via the convenicent script:

curl -fsSL https://raw.githubusercontent.com/melonattacker/logira/main/install.sh | sudo bash

Option2. Manual install from a release tarball:

tar -xzf logira_vX.Y.Z_linux-<arch>.tar.gz
cd logira_vX.Y.Z_linux-<arch>
sudo ./install-local.sh

After reinstall / upgrade:

  • First install: no extra step is usually needed (install.sh runs systemctl enable --now).
  • Reinstall/upgrade over an existing install: restart logirad to ensure the new binary is running.
sudo systemctl daemon-reload
sudo systemctl restart logirad.service
sudo systemctl status logirad.service --no-pager

from source

Build:

make build

Start the root daemon (required for tracing):

sudo ./logirad
How to run `logirad` via systemd

To run the root daemon in the background, install the unit file from packaging/systemd/logirad.service.

# 1) Generate eBPF objects (only needed if missing)
make generate

# 2) Install the systemd unit
sudo install -D -m 0644 packaging/systemd/logirad.service /etc/systemd/system/logirad.service

# 3) Install the daemon binary (unit defaults to /usr/local/bin/logirad)
sudo install -m 0755 ./logirad /usr/local/bin/logirad

# 4) (Recommended) Point systemd at the eBPF .o files via an environment file.
# This avoids relying on the service working directory.
sudo mkdir -p /etc/logira
sudo tee /etc/logira/logirad.env >/dev/null <<'EOF'
LOGIRA_EXEC_BPF_OBJ=/absolute/path/to/collector/linux/exec/trace_bpfel.o
LOGIRA_NET_BPF_OBJ=/absolute/path/to/collector/linux/net/trace_bpfel.o
LOGIRA_FILE_BPF_OBJ=/absolute/path/to/collector/linux/filetrace/trace_bpfel.o
EOF

# 5) Enable + start
sudo systemctl daemon-reload
sudo systemctl enable --now logirad

# Follow logs
sudo journalctl -u logirad -f

# Check status
systemctl status logirad --no-pager

# Stop + disable
sudo systemctl stop logirad
sudo systemctl disable --now logirad

Usage

Run an agent under audit as your normal user (events are auto-saved):

./logira run -- bash -lc 'echo hi > x.txt; curl -s https://example.com >/dev/null'
./logira run --rules ./my-rules.yaml -- bash -lc 'cat ~/.aws/credentials >/dev/null'

Run Codex CLI:

./logira run -- codex --yolo "Update the README to be clearer and add examples."

Run Claude Code CLI:

./logira run -- claude --dangerously-skip-permissions "Find and fix flaky tests."

List runs:

./logira runs

View and explain the last run:

./logira view last
./logira view last --ts both
./logira view last --color always
./logira explain last
./logira explain last --show-related
./logira explain last --drill 35
./logira report last
./logira report last --exec-seq 12

Query events:

./logira query last --type detection
./logira query last --type net --dest 140.82.121.4:443
./logira query last --related-to-detections --type net
./logira query last --contains curl

Commands

  • logira run -- <command...>: run a command under audit and auto-save a new run
  • logira runs: list saved runs
  • logira view [last|<run-id>]: run dashboard (use --raw for legacy text)
  • logira query [last|<run-id>] [filters...]: search events with type-specific table output
  • logira explain [last|<run-id>]: grouped detections by default (--show-related, --drill)
  • logira episode [last|<run-id>] --exec-seq <seq> [--json]: reconstruct one observed execution lineage
  • logira report [last|<run-id>] [--exec-seq <seq>]: generate a standalone offline HTML audit report

Execution Episodes

A Run contains the capture session's retained observations. A Process Graph reconstructs observed task identities and relationships within that Run. An Execution Episode selects one exec and follows its observed descendants, including fork-only tasks and later executable replacements.

./logira query last --type exec
./logira episode last --exec-seq 12
./logira episode last --exec-seq 12 --json

Episodes report attributable file/network evidence and explicitly separate uncertain, unrelated, and unattributable observations. Ancestors and siblings do not become members. Missing ancestry or empty activity does not prove inactivity. This is offline, general-purpose OS analysis, independent of agent runtimes and without security or intent judgments.

See Episode identity, attribution, counting, and JSON semantics for the stable output format, legacy limitations, and a shell/descendant example.

Standalone HTML Reports

Generate a Run Overview without selecting an execution:

./logira report last

Select an observed exec sequence to add its Execution Episode:

./logira query last --type exec
./logira report last --exec-seq 12 --output ./audit.html

Reports are single offline HTML files with embedded CSS and no external runtime dependencies. They preserve Episode attribution and uncertainty boundaries, show capture limitations, and include CLI handoffs to retained source events. They may contain sensitive commands, paths, and network destinations.

Scarica lo strumento

Più Popolari

Vedi tutti →

Scopri gli strumenti più utilizzati dalla nostra community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 Il toolkit OSINT definitivo: grafo di indagine, punteggio di affidabilità, famiglie di alias, mappa, timeline e report. 49 moduli, oltre 400 siti, nessuna chiave API richiesta.

    837
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # App di esecuzione con un tocco GhostLock (CVE-2026-43499)

    536
  • 3

    ARTEX

    baarai/artex

    Piattaforma di penetration testing autonoma multi-agente basata su LLM con agenti planner/worker, grafi di asset e di esplorazione, registrazione del traffico MITM e retesting delle vulnerabilità.

    424
  • 4

    redforge

    cybersecurity91/redforge

    Toolkit red team lato browser con 102 strumenti offline per ricognizione, generazione di payload, attacchi alle credenziali, crittografia, codifica e reportistica dell'engagement.

    355
  • 5

    looking-glass

    anonghosty/looking-glass

    Piattaforma CSIRT che importa i report di Shadowserver in MongoDB e li riproduce come mappe interattive, analisi, risultati, avvisi e dashboard executive.

    294
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    Il sistema d'azione per la cybersecurity nativa AI—dove l'intento diventa esecuzione governata, le evidenze diventano memoria operativa, e ogni operazione migliora la successiva.

    276

Esplora tutti gli strumenti

Sfoglia la nostra collezione di strumenti

Vedi tutti gli strumenti →