exploit_dataset: move retired ATLAS IDs to AML.T0115 sub-techniques

[emmanuelgjr]

Summary

MITRE ATLAS release 2026.07 retired three technique IDs the exploit dataset uses. It merged them into a new technique, AML.T0115 Publish Poisoned AI Artifacts, and renamed AML.T0020 in the same release (ATLAS changelog, 2026.07):

Retired	Now
AML.T0019 Publish Poisoned Datasets	AML.T0115.000 Publish Poisoned AI Artifacts: Datasets
AML.T0058 Publish Poisoned Models	AML.T0115.001 Publish Poisoned AI Artifacts: Models
AML.T0104 Publish Poisoned AI Agent Tool	AML.T0115.002 Publish Poisoned AI Artifacts: AI Agent Tools
AML.T0020 Poison Training Data (name)	AML.T0020 Training Data Poisoning

Changes:

• entries/AML.T0019.json → entries/AML.T0115.000.json and entries/AML.T0058.json → entries/AML.T0115.001.json. In each, exploit_id, title, mitre_atlas_mapping and the ATLAS source URL are updated. A new notes field records the old ID, so a search for it still finds the entry. Everything else in the entries is unchanged.
• AML.T0110.json and DSGAI-EXP-rome-targeted-fact-editing.json: the ATLAS mappings now use AML.T0115.002 and AML.T0115.001.
• AML.T0020.json: the title follows the ATLAS rename.
• index.csv is regenerated with build_index.py.

Found by the ATLAS reference check in #89.

Verification

• python validate.py in datasets/exploit_dataset: all 59 entries pass.
• data_validation: implement the validators and QC tools, fix reference data #89's crossref_validator on this dataset: 0 errors. The 2 remaining warnings are the intentional old-ID mentions in the new notes fields.
• data_validation: implement the validators and QC tools, fix reference data #89's consistency_check: no dangling references. Nothing else in the repo cited these exploit IDs.

Checklist

• Validation scripts pass
• Entries reference at least one DSGAI ID (unchanged)

🤖 Generated with Claude Code