Fetching from the wire…
Public story · 2026-09-08 · high
SHAP explanations score a coalition game, not a file's real behavior, and split credit for redundant features by exactly 1/m.
Why now: The proof arrived as SHAP still backs the explanations security vendors give for malware verdicts.
A new proof argues SHAP scores a coalition game, not a file's real behavior, when it explains why a malware classifier flagged something. That distinction carries a real cost: the game only stays fixed once someone picks the players, the missing-feature rule, the background distribution and the input mapping, and conditional SHAP splits credit for one real signal by 1/m across m-1 redundant features carrying that same information, per arXiv preprint 2609.04626.
Static PE feature spaces make the dilution worse. Byte histograms, entropy scores, strings, headers, sections and imports aren't independent. File structure, packing and compiler behavior shape several of them at once, so a feature doing all the real detection work can end up looking like it barely matters once SHAP spreads its credit across every correlated stand-in.
The paper also proves a sharper point. Under distribution shift, conditional SHAP can reverse the attribution sign on a feature the model never uses at all. A feature the detector ignores can show up in the explanation pushing the verdict the opposite direction from what a second run, on a different background distribution, would show. Neither failure needs a bug. SHAP is working exactly as built, on a game that was never designed to match the detector's real decision.
Each link below shares sources, entities, or timing with this story.
arXiv 2609.03826. Unsupervised detectors give you a score and nothing else, and SHAP or LIME get bolted on afterward at thousands of detector re-queries per point for an approximation. WAND scores each point by how far its projection escapes a sub-Gaussian extreme-value baseli...
Using CoderForge-Preview, described as the largest open dataset of coding agent trajectories, ensemble methods with SHAP attribution predict agent success before any run. Dominant drivers are patch fragmentation (how many places a fix has to touch) and repository scale. Prompt...
AWS details a banking next-best-product system with four specialized towers: a 2-layer GRU over product adoption history plus MLP towers for transactions (7/30/60/180/365-day windows), demographics, and behavioral segmentation, each emitting a 64-dim vector fused by multihead...
arXiv 2608.11632 argues storage retention doesn't identify *authoritative* state: unmediated updates by models, tools, and background workers cause stale overwrites and self-authorizing privilege escalation. Untrusted components propose typed changes against an exact predecess...
The PAI combines Evaluation, Context, Compliance, and Governance into a release-gate index. Three findings cut against current practice: context engineering strongly changes reliability, capability improves behavior but doesn't determine readiness, and governance evidence degr...
SEPO argues API-only prompt optimizers are inspectable only after the fact, since each iteration rewrites the prompt as one opaque string. Instead it edits stable typed units in a two-layer schema, links each edit to the examples it newly fixes or breaks, and carries that line...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.