Model integrity is not confined to the visible transformer weight file. In architectures that retrieve learned memory entries through a gate, the auxiliary lookup values participate directly in inference. BadEngram shows how altering those values and their gating logic can direct selected triggers toward attacker-chosen outputs even when the primary…
Inspect the ClaimsCase · DiggingBeagle record
BadEngram backdoors model memory tables without changing backbone weights
BadEngram changed auxiliary gated model-memory components while the main transformer weights remained unchanged, producing triggered behavior in controlled models.
Researcher-controlled Engram and related architectures with write access to auxiliary memory tables or gates. Distinct model configurations produced different reported trigger rates; no live third-party checkpoint compromise demonstrated.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- demonstrated
- Impact
- Band 2 of 4
- Evidence
- Grade B
- Remediation
- mitigation available
- AI role
- AGAINST AI
Basis and provenance
The original and Fujitsu disclosures describe memory-table and gate backdoor tests with main model weights untouched and ablation reducing success in tested settings. The prior null rating described absent field losses; this bounded rating covers observed triggered behavior only. Signing and auditing all ancillary model state are prospective mitigations, not a verified widespread fix.
Impact basis: A controlled attacker with write authority over auxiliary memory tables or gates can change conditional model behavior at substantial reported trigger rates. Band represents an experimentally reproduced model-integrity boundary, not compromised third-party deployments or measured victims.
Assessed Oct 19, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CP5-BADENGRAM-MEMORY-BACKDOOR-1 · CLM-CP5-BADENGRAM-MEMORY-BACKDOOR-2 · CLM-CP5-BADENGRAM-MEMORY-BACKDOOR-3 · CLM-2026-BADENGRAM-FUJITSU-OCT-CROSSMODEL · BadEngram: Backdoor Attack on Gated Memory Components in LLMs, arXiv v2 · Fujitsu and Pillar research on BadEngram auxiliary memory poisoning
At a glance
A backbone checksum covers only one portion of the model actually loaded. Memory lookup tables, gates and auxiliary assets can carry behavior that a weight-only review misses. The demonstrated decrease in attack success when the researchers restore clean memory or close its gates identifies the causal route in that setup; it does not prove that disabling…
Read the implicationsNo real downstream compromised checkpoint or deployed backdoor was established. Actual prevention depends on integrity and loading policies for all model-side assets, not only the backbone.
Limits and uncertaintyFull account
Model integrity is not confined to the visible transformer weight file. In architectures that retrieve learned memory entries through a gate, the auxiliary lookup values participate directly in inference. BadEngram shows how altering those values and their gating logic can direct selected triggers toward attacker-chosen outputs even when the primary backbone hash remains unchanged.
The original controlled Engram result reported 96.6% triggered success with low false activation and unchanged clean-task behavior under the stated evaluation. Fujitsu's later technical discussion described additional experiments on native memory mechanisms with materially different rates and prerequisites. These percentages cannot be pooled or used as a prevalence estimate for deployed models. The experiment required control over the auxiliary artifact, and did not establish that a hosted provider or model registry had been compromised.
The important verification unit is the complete loadable model, including offloaded N-gram stores, gating parameters and any caches that affect output. A signature over the backbone alone does not establish the integrity of the instantiated inference system. Conversely, the presence of a writable cache does not prove that it contains a backdoor without comparing its content, source and triggered behavior.
Claims & evidence
CLM-CP5-BADENGRAM-MEMORY-BACKDOOR-1In a controlled Engram model, researchers report 96.6% triggered attack success, 0.1% false activation and 99.6% clean accuracy.supported
Basis: reported finding
- supportsBadEngram: Backdoor Attack on Gated Memory Components in LLMs, arXiv v2primary disclosure
Abstract: controlled Engram feasibility and results
CLM-CP5-BADENGRAM-MEMORY-BACKDOOR-2They separately tested a native per-layer memory subsystem in Qwen3.8-Flash-Next, reporting 47.8% HarmBench and 64.0% AdvBench attack success using independently trained checkpoints.supported
Basis: reported finding
- supportsBadEngram: Backdoor Attack on Gated Memory Components in LLMs, arXiv v2primary disclosure
Abstract: production-scale native per-layer embedding tests
CLM-CP5-BADENGRAM-MEMORY-BACKDOOR-3Replacing modified memory values or closing gates reduced observed attack success to at most 0.32% in the controlled configuration.supported
Basis: reported finding
- supportsBadEngram: Backdoor Attack on Gated Memory Components in LLMs, arXiv v2primary disclosure
Abstract: gated-memory intervention and ablation
CLM-2026-BADENGRAM-FUJITSU-OCT-CROSSMODELFujitsu and Pillar reported controlled trigger-dependent BadEngram behavior on DeepSeek-V4.1-Flash as well as the documented Qwen3.8 and adapted DeepSeek-7B systems, without changing the main model backbone.supported
Basis: reported finding
- supportsFujitsu and Pillar research on BadEngram auxiliary memory poisoningprimary disclosure
Demonstration Results, paragraphs on DeepSeek-7B, Qwen3.8-Flash-Next, and DeepSeek-V4.1-Flash
Implications
A backbone checksum covers only one portion of the model actually loaded. Memory lookup tables, gates and auxiliary assets can carry behavior that a weight-only review misses. The demonstrated decrease in attack success when the researchers restore clean memory or close its gates identifies the causal route in that setup; it does not prove that disabling all memory modules is a practical production solution.
Controls and mitigations
- Pin and hash model memory tables, gate parameters and other auxiliary artifacts together with the backbone and loader configuration; verify the complete asset set at loading.
- Use controlled trigger tests and clean-memory comparisons when evaluating suspicious gated-memory behavior, while treating absence of tested triggers as limited negative evidence.
Unknowns and contradictions
- No real downstream compromised checkpoint or deployed backdoor was established.
- Actual prevention depends on integrity and loading policies for all model-side assets, not only the backbone.
Sources and citation
Material revision history
- Oct 19, 2026 · Published version · first publication · revision 174
- Oct 19, 2026 · Canonical change recorded · material revision · revision 175Public fields changed: assessment_profile