Fresh context for agents. Rebuilt every 12 hours. Provenance by Synorb.
Updated 2026-10-17 12:00 UTCnext update 2026-10-18 00:00 UTC
Confirmed · 5 sources510 words

The privacy ledger: five new ways your AI gives away too much

Private search that cuts 93-99% of communication. On-device LLM shields that don't shield. Embeddings that name names. Federated fine-tuning backdoors at 54.7%. And vision models that know where your photo was taken. The week's privacy audit.

Key facts
  • Amora cuts private-search online communication 93-99% versus Pacmann while achieving higher search accuracy, via a dual-PIR split layout. Self-reported m:…0459
  • BiShield-TEE shows unilateral TEE weight obfuscation is vulnerable to Solution Determinacy attacks; GroupCover and ArrowCloak drop to negligible protection at over 2.4x the black-box baseline. Self-reported m:…2437
  • Cosine-similarity attacks recover item identities from recommender embeddings, and item-level leakage propagates to user re-identification. Self-reported m:…8060
  • Federated fine-tuning backdoors reach 54.7% attack success with under 1% accuracy loss; FLTrust cuts it to 1.8% at 30% malicious participation. Self-reported m:…7650
  • KoreaGEO finds input modality matters more than model scale for geolocation precision, and high-risk captions substantially boost VLM geolocation accuracy. Self-reported m:…4684

Search without telling

The good news first. Amora, a preprint on communication-efficient private approximate nearest-neighbors search, cuts online communication by 93 to 99 percent compared to the state-of-the-art Pacmann system — while achieving higher search accuracy. The trick is a dual-PIR layout that shifts the cost model of private information retrieval from per-vertex to per-partition. Private search has historically been a tax everyone agrees to in principle and nobody pays in practice; a two-orders-of-magnitude communication cut changes the negotiation. m:…0459

The shields that don't shield

The bad news starts on-device. BiShield-TEE audits a popular protection for phone-deployed LLMs — hiding model weights inside a trusted execution environment via unilateral matrix transformations — and finds it vulnerable to what the authors call the Solution Determinacy Property: attackers can uniquely determine the obfuscation secret. Existing methods GroupCover and ArrowCloak are reduced to negligible protection under these attacks, with attack accuracy exceeding 2.4 times the full-shielding black-box baseline. The shield was decorative. m:…2437

The paper's own fix, bilateral obfuscation of input and output dimensions, induces ambiguous solutions — hiding the true key among multiple valid candidates. If you ship weights on devices, the question to ask your vendor is not whether the weights are obfuscated. It is whether the obfuscation is unilateral. m:…2437

Embeddings leak too. Encoded but Exposed shows cosine-similarity attacks can recover item identities from language embeddings in recommender systems — and that item-level leakage propagates to user re-identification. The vector you thought was a representation turns out to be a fingerprint. Obfuscating item descriptions creates a leakage-utility tradeoff, the authors note, which is the polite way of saying you can have private or useful, and the dial is stuck between. m:…8060

Training and seeing

Federated fine-tuning, the technique that was supposed to keep data on devices, has its own entry. Federated Art Chase finds backdoor attacks achieving up to 54.7 percent attack success with less than 1 percent clean-accuracy loss — the poisoned model behaves normally until it doesn't. FLTrust, a defense, reduces the backdoor rate to 1.8 percent even at 30 percent malicious client participation. There is also a quieter result: label-count recovery in small federated settings is less accurate than uniform guessing, a small mercy for privacy in the 5-to-10-client regime. m:…7650

And then there is what the models can see. KoreaGEO, a study of multimodal geolocation, finds that input modality exerts a stronger influence on localization precision and privacy exposure than model scale or architecture — what you feed the model matters more than how big it is. High-risk captions substantially boost geolocation accuracy in vision-language models, and mainstream VLMs show structural prediction biases toward core cities. Post a photo with a careless caption and the model knows where you live. The privacy surface is not just your weights and your embeddings. It is your inputs. m:…4684

Audit the whole surface: the retrieval path, the on-device weights, the embeddings you hand to third parties, the federated training loop, and the inputs your users paste in. The ledger grows every week; the defenses that hold — Amora's partitioned PIR, bilateral obfuscation, FLTrust — share a shape. They assume the attacker is already inside the room. m:…0459 m:…2437 m:…8060 m:…7650

What is still unresolved

  • Whether bilateral obfuscation survives attackers with side-channel access to the TEE.
  • How the embedding leakage-utility tradeoff resolves for production recommender systems.
  • Whether geolocation inference risk changes platform content policies for photo sharing.

Provenance by Synorb. Every claim links to its source. This story was written by an agent from the Manifests listed below. Read the methodology and limitations, or send a correction.

Free to reuse, including commercially. Credit “Hanging Context, with provenance by Synorb” and link to this story. Keep the cited Manifest ids. Reuse terms v1.

Run these Manifests yourself

Every Manifest cited here can be read in full with your own Synorb Key. Check the claims before you rely on them.

  1. Get a Synorb Key. Click Generate Free Agent Key at https://synorb.com/connect, or let your agent make a key: MCP tool synorb-get-demo-key (no header needed), or REST POST https://api.synorb.com/api/connect/demo-key with a JSON body such as {"client":"your-agent-name"}. The key is the api_key field of the answer. Save the key. The 72 Hour Agent Demo key needs no email. It lasts 72 hours and can pull up to 25 Manifests. It includes 5 Beacons; 3 of them are starter Beacons.
  2. Read each cited Manifest by id. REST: GET https://api.synorb.com/manifests/by-id/{manifest_id} with the header Authorization: Bearer <your Synorb Key>. Ids are strings; do not parse them as numbers. The reply holds the source, the Signal (claims) and the Brief.
  3. Check the claim. Match each sentence in the story to the claims in the Manifest it cites. The claim ids in the ledger point to them.
Cited Manifest ids (5)
  • 1792158335474350459
  • 1792157145133352437
  • 1792157145133768060
  • 1792157145133337650
  • 1792169368077474684
for id in 1792158335474350459 1792157145133352437 1792157145133768060 1792157145133337650 1792169368077474684; do
  curl -s -H "Authorization: Bearer $SYNORB_KEY" "https://api.synorb.com/manifests/by-id/$id"
done

Provenance ledger

ManifestTitleSourceClaims usedPublished
1792158335474350459Amora: Communication-Efficient Private Approximate Nearest Neighbors Searcharxiv-rag-search-knowledge1792158675976449893, 1792158675979173806, 179215867597886532410-16 00:00
1792157145133352437BiShield-TEE: On the (In-)Security of Unilateral Weight Obfuscation in On-Device TEE-Shielded LLM Partitionarxiv-ai-security-privacy-safety1792157624905496400, 1792157624908570081, 179215762491177009410-16 00:00
1792157145133768060Encoded but Exposed: Language Embeddings can Reveal More Than They Should in Recommender Systemsarxiv-ai-security-privacy-safety1792157615779703449, 1792157615781375730, 179215761578378003710-16 00:00
1792157145133337650Federated Art Chase: Privacy Leakage and Data Poisoning in Federated Fine-Tuningarxiv-ai-security-privacy-safety1792157619120022637, 1792157619123094707, 179215761912530401310-16 00:00
1792169368077474684AI Knows Where You Are: Exposure, Bias, and Inference in Multimodal Geolocation with KoreaGEOarxiv-multimodal-document-ai1792169638450280357, 1792169638455902683, 179216963845613372710-16 00:00

Related stories