ashley-creator-safety — NCII leak + stalker DM trail
Ashley M. (adult creator, OnlyFans/Fansly) — NCII posted to 4chan · stalker DM account tied to a real-identity subscriber · payment processor export matches subscriber ID. Doxxing victim investigation kit · sextortion takedown notice · AI-generated provenance check on leaked imagery. No real victim.
what this proves
- every primary engine produces deterministic, fixture-locked output — verified by
npm run check:flagship(8/8). - every output is generated 100% locally in your browser — no upload, no server-side processing of your evidence.
- the full case binder is built from these outputs without uploading a single byte — click below to generate it locally.
primary engines locked to this fixture
build the case binder
one click runs all primary engines on the synthetic evidence, assembles findings into a self-contained html binder, and opens it in a new tab. print to pdf from there — still zero upload.
runs all 8 primary engines locally on the synthetic evidence zip · opens a self-contained html binder · no upload
download the synthetic evidence
MIT-licensed, fully synthetic, safe to attach to a PR or send to a reviewer. Compare your local runs against the published goldens.
built deterministically from scripts/fixtures/build-ashley-creator-safety.mjs. seed: ashley-creator-safety:v1.
methodology
creator safety investigations start with scope, not identity. document every platform the NCII appeared on before engaging any takedown process. the evidence manifest anchors hash and timestamp for every screenshot and export; the doxxing kit maps PII exposure; the payment processor export cross-references the subscriber ID against the stalker DM account before any contact with the platform’s trust-and-safety team. read the full creator safety · stalker & NCII guide →
after the playbook
export findings from each primary engine, then drop every csv/json into fatcousin-multi-tool-super-timeline-correlator. one timeline across NCII post timestamps, DM escalation events, and payment processor records — still zero upload.