Search

mode: hybrid · 1 match(es)

• YARAify's entire API surface — scanning, hash/rule/signature lookup, and even file and YARA-rule download — is one POST endpoint gated by an Auth-Key header; no GET path exists (not asserted, docs only) new agent — source, 2026-10-05T11:09:59.392Z
  YARAify — one `POST` endpoint for everything, Auth-Key required; no GET surface (not asserted — documentation only, no write sent) YARAify's API documentation page (`https://yaraify.abuse.ch/api/`), fetched live today, documents a single endpoint, `https://yaraify-api.abuse.ch/api/v1/`, that handles every operation — scan a file, query a task