Catalog
| Binary | Functions | Type | OS | Verified | Readiness |
|---|
Scope
LOL-GAI (Living Off Legitimate GenAI) is a living-off-the-land catalog of GenAI-related binaries and tooling that may appear on developer workstations and endpoints as adoption grows — named as a deliberate play on LOLBins (legitimate GenAI tools, same class of problem). Oriented toward detection engineering: what runs, where it lives, how to attribute it, and how those surfaces can be abused.
In scope
- Terminal / CLI binaries with an observable process name
- Companion helpers (tunnels, updaters) when abuse or attribution differs
- Install paths, config dirs, network destinations, and signing/origin signals
- Documented abuse recipes and ranked attribution signals
Out of scope
- IDE-only chat UIs with no distinct process (unless a binary ships)
- Cloud SaaS with no host footprint
- Generic language runtimes (python, node) without a GenAI-specific entrypoint
Catalog readiness (A/B/C)
The Readiness column is an editorial grade: how useful this YAML entry is for detection engineering, not how dangerous the tool is. It reflects binaries, host artifacts, abuse recipes, ranked attribution signals, and (for Grade A) whether you can reliably attribute the process on an endpoint.
| Grade | Meaning |
|---|---|
| A | Detection-ready: full binaries, artifacts, recipes, and signals, plus strong attribution, usable signing (full / authenticode depth) or a high-reliability, product-specific signal (not shared VS Code Code Helper or generic process.name alone). |
| B | Solid entry: binaries, paths, recipes, and attribution signals are present; attribution is usable but does not meet Grade A bar (weak signing, shared host, or corroboration-heavy signals). |
| C | Partial or sparse: a useful catalog pointer; may lack lab depth, strong signals, or full artifact coverage. |
Readiness ≠ Verified. The Verified column is VerificationLevel in YAML: how the entry was checked: Unverified (stub), Documented (official docs / --help), or Observed (lab host: paths, signing, or binary behavior). An Observed tool can still be Grade C if metadata is thin; a Documented stub can be Grade B if fields are complete.
Contribute
Source and pull requests: https://github.com/Mikaayenson/lolgai · Site: lolgai.io
See CONTRIBUTING.md for the full checklist.
One YAML file per tool (or per surface when abuse differs). Do not edit tools.json by hand; it is generated at build time.
- Fork the repository and create a branch
- Add yaml/<vendor>/<tool>.yaml from the template
- Set Author to your GitHub handle; when editing an existing entry, keep the original Author and add yourself under Contributors
- Include binaries, functions, abuse recipes, attribution signals, and artifacts
- Do not submit vendor query languages or sample SIEM rules
- Open a pull request. CI validates the schema
About
LOL-GAI (Living Off Legitimate GenAI) is a living-off-the-land catalog of GenAI binaries on developer workstations and endpoints — a deliberate play on LOLBins, not a mistype of “land.” Attribution signals, artifacts, abuse recipes, and observable datapoints for detection engineering.
Maintained by Mika Ayenson, who leads the Threat Research and Detection Engineering (TRaDE) team at Elastic with a focus on AI Security. With a background in Cyber Missions Operations at JHUAPL, Ayenson keeps LOL-GAI as a personal catalog as GenAI adoption maps to new endpoint and SIEM detection surfaces.