LLMs Can Leak Training Data But Do They Want To? A Propensity-Aware Evaluation of Memorization in LLMs

· Source: cs.AI updates on arXiv.org · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Cybersecurity & Data Privacy · Depth: Expert, extended

Summary

The PropMe framework and SimpleTrace pipeline introduce a propensity-aware evaluation for Large Language Model (LLM) memorization, contrasting prefix-based capability attacks with non-adversarial use. PropMe proposes a metric transformation for existing functions, while SimpleTrace, built on infini-gram, deterministically attributes generations to training corpora and computes verbatim, near-verbatim, and propensity-transformed metrics. Evaluating Comma and DFM Decoder models on Common Pile and Dynaword datasets, researchers found a consistent gap: prefix attacks elicited substantially stronger memorization signals than generic or dataset-specific prompts, with overall low propensity scores. DFM Decoder, continually pre-trained from Comma, exhibited reduced memorization and propensity for Common Pile, suggesting memorization capability can decrease with training on partially different data.

Key takeaway

For AI scientists and ML engineers developing or deploying LLMs, you should integrate both capability and propensity evaluations into your memorization audits. Relying solely on worst-case extractability overstates practical leakage risks, while ignoring it misses critical vulnerabilities. Your audits should report both to provide a comprehensive view of data leakage, especially for legal compliance under regulations like GDPR and the EU AI Act.

Key insights

LLMs can leak training data under adversarial prompts but rarely do so in ordinary, non-adversarial use.

Principles

Method

PropMe contrasts generic/specific prompts (propensity) with prefix attacks (capability), applying a transformation to standard metrics. SimpleTrace traces model outputs to training data using infini-gram for deterministic attribution.

In practice

Topics

Code references

Best for: Research Scientist, CTO, VP of Engineering/Data, AI Scientist, Machine Learning Engineer, AI Ethicist

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.AI updates on arXiv.org.