loldrivers.io valid

LOLDrivers

LOLDrivers (Living Off The Land Drivers) is a community-maintained catalog of vulnerable and malicious Windows drivers. It provides sample hashes, metadata, research references, and detection resources for investigating driver abuse, including bring-your-own-vulnerable-driver (BYOVD) attacks.

For agents: Community catalog of vulnerable and malicious Windows drivers with hashes, metadata, detections, and a JSON/CSV API feed for security investigation.

vulnerable-driversbyovdwindows-malwarethreat-intelligencedriver-hashessecurity-research

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T15:28:21.059Z. Cached copy · Source on loldrivers.io

# LOLDrivers

> LOLDrivers (Living Off The Land Drivers) is a community-maintained catalog of vulnerable and malicious Windows drivers. It provides sample hashes, metadata, research references, and detection resources for investigating driver abuse, including bring-your-own-vulnerable-driver (BYOVD) attacks.

Use this guide to find driver evidence, published data, and defensive resources. Distinguish a vulnerable driver from a malicious driver, and verify the exact sample and hash before applying a record to a file. Individual samples can have different vulnerability or hypervisor-protected code integrity (HVCI) evidence; missing evidence means unknown. Cite the driver record and its original research references for specific claims.

## Catalog and research

- [LOLDrivers overview](https://www.loldrivers.io/): Project overview, catalog metrics, recent entries, and the driver explorer. Start here for the scope of the project.
- [Driver directory](https://www.loldrivers.io/drivers/): Browse driver records and follow individual pages for sample hashes, signatures, references, and detections.
- [Search](https://www.loldrivers.io/search/): Look up filenames, publishers, CVEs, record identifiers, and sample hashes. Use when investigating a particular driver.
- [About LOLDrivers](https://www.loldrivers.io/about/): Project background, maintainers, and community context.

## API and structured data

- [API documentation](https://www.loldrivers.io/api/): JSON and CSV download guidance and field interpretation. Read this before integrating the feed, especially its category, sample, and HVCI fields.
- [Driver JSON feed](https://www.loldrivers.io/api/drivers.json): Published records with sample hashes, signatures, and metadata. Use for programmatic lookups and bulk enrichment.
- [Driver CSV feed](https://www.loldrivers.io/api/drivers.csv): Flattened tabular export. Use for spreadsheet analysis and integrations that require CSV.
- [Record schema](https://raw.githubusercontent.com/magicsword-io/LOLDrivers/main/bin/spec/drivers.spec.json): Source schema for driver records. Use to understand field structure and validation requirements.
- [Source records](https://github.com/magicsword-io/LOLDrivers/tree/main/yaml): YAML records behind the site and feeds. Use for source references and change history.

## Detections and defensive tools

- [Detection guidance](https://www.loldrivers.io/detections/): Detection resources and hunting queries. Use for integrating LOLDrivers evidence with existing telemetry.
- [Detection repository](https://github.com/magicsword-io/LOLDrivers/tree/main/detections): Sigma, YARA, ClamAV, Sysmon, and other defensive resources. Consult the individual files for their scope and requirements.
- [WDAC policies](https://github.com/magicsword-io/LOLDrivers/tree/main/detections/wdac): Windows Defender Application Control policy resources. Review the policy contents and applicability before deployment.
- [Community tools](https://www.loldrivers.io/to
…

Related sites

Other listed sites in Cybersecurity. See the whole category →

Machine-readable: GET /v1/resolve?q=loldrivers.io · GET /v1/domain/loldrivers.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for loldrivers.io:
1. POST https://agentwebmap.com/v1/sites/loldrivers.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://loldrivers.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/loldrivers.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/loldrivers.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.