Lock in place.
Reading a decoy on the local drive triggers a lock across eligible customer files. The originals are replaced by .dye files, and apps see that the plaintext file is gone. Run dyepack unlock to restore the bytes.
Data Dyepack
An agent opens a decoy. Dyepack locks customer files in place and gives the team a trail to follow.
How it works
When an AI agent with a stolen login sweeps through customer records, a decoy file or planted identity can reveal what it touched. The Lakeview Fiber lab shows how those signals work together.
Reading a decoy on the local drive triggers a lock across eligible customer files. The originals are replaced by .dye files, and apps see that the plaintext file is gone. Run dyepack unlock to restore the bytes.
Measured in the lab
The demo measures detection separately from containment. The agent tripped a decoy in a few hundredths of a second, then Dyepack locked the eligible files in place.
In the recorded trial, the served model missed the real list among five candidates. A later canary login identified the exact export it came from.
Get started
Use Python 3.10 or newer. The lab runs on the standard library. All customer data is generated for the demo.
git clone https://github.com/Durovo51/Data-Dye-Pack.git &&
cd Data-Dye-Pack &&
([ -f .env ] || cp .env.example .env)
Set DYEPACK_LOCK_PASSWORD in .env before building the drive. For the shorter dyepack command, use an editable install with python3 -m pip install -e .
python3 -m dyepack lab &&
python3 -m dyepack seed &&
python3 -m dyepack drive &&
python3 -m dyepack serve --open
In another terminal at the repo root, try normal support activity, the stolen-login scenario, or the agent scenario.
python3 -m dyepack drill normal
python3 -m dyepack drill heist
python3 -m dyepack drill agent --simulate-sentinel
For live file reads, add the sentinel and run the agent drill without simulation. On Linux, use python3 -m dyepack sentinel. On macOS, give your terminal Full Disk Access and use sudo python3 -m dyepack sentinel.
Restore the lab files afterwards with python3 -m dyepack unlock.
Databricks integration
A served Databricks chat model can write incident reports and triage. Delta tables hold the alert history for dashboards and Genie questions. With no Databricks credentials configured, the lab uses local report templates.
Configure reports and notifications.envDATABRICKS_HOSTDATABRICKS_WAREHOUSE_IDDATABRICKS_MODELDATABRICKS_TOKENPython 3.10+, Databricks Model Serving, Delta and Genie, SQLite customer tables, CSV and JSON files, Linux inotify and auditd, and the macOS system event stream.
The project runs as a single-machine hackathon lab. Here’s what would need to change for production.
The lab uses synthetic customers. A deployment would use company-controlled canary email addresses and phone numbers to receive contact attempts.
The lab gets its lock password from .env. A production deployment would keep the secret in a separate key manager and require two people to authorize an unlock.
The plausibility of a fake list depends on how well its distribution matches the population. A production header would draw from an independent population model to avoid giving away patterns in the protected data.
Lock in place currently targets eligible customer-shaped CSV and JSON files. SQLite holds the lab database. Linux inotify reports file activity without process names. Process matching is available on macOS or through the Linux auditd bridge.
Records returned before lockout can already be exposed. Dyepack reports activity it observed and can identify a stolen export when a planted identity is used.