<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>DT.gl Digital Trust &amp; Threat Lab</title>
  <id>https://dt.gl/</id>
  <link href="https://dt.gl/atom.xml" rel="self" />
  <link href="https://dt.gl/" />
  <updated>2026-11-11T00:00:00Z</updated>
  <author><name>DT.gl Digital Trust &amp; Threat Lab</name></author>
  <entry>
    <title>Commercial Data Brokers, Mobile Location Telemetry, and Full-Spectrum Anti-Tracking Engineering (2026)</title>
    <id>https://dt.gl/anti-tracking/data-brokers-telemetry</id>
    <link href="https://dt.gl/anti-tracking/data-brokers-telemetry" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Commercial data brokers harvest sub-meter mobile coordinates through Real-Time Bidding advertising SDKs, Bluetooth beacons, and vehicle telematics, historically selling warrantless movement graphs to government agencies and private aggregators. Effective 2026 defense combines FTC sensitive-location prohibitions, California DROP statutory deletion, OS advertising-ID zeroing, cellular 2G baseband lockouts, and strict compartmentalization of residential KYC records.</summary>
  </entry>
  <entry>
    <title>Decentralized Social Protocols, Self-Hosted Publishing &amp; Privacy Frontends: 2026 Audit</title>
    <id>https://dt.gl/privacy/decentralized-protocols</id>
    <link href="https://dt.gl/privacy/decentralized-protocols" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Decentralized publishing protocols trade corporate platform lock-in for distinct cryptographic key-management and metadata trade-offs. ActivityPub binds identity to domain-controlled servers, Nostr anchors identity in raw secp256k1 keypairs across dumb relays without native rotation, and AT Protocol introduces rotatable DIDs over verifiable repositories, yet every public federated firehose permanently replicates metadata unless paired with strict endpoint hygiene.</summary>
  </entry>
  <entry>
    <title>Encrypted DNS, TLS ECH &amp; Network Metadata Defense: 2026 Protocol Architecture</title>
    <id>https://dt.gl/anti-tracking/encrypted-dns-network</id>
    <link href="https://dt.gl/anti-tracking/encrypted-dns-network" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Encrypting DNS stops local ISP packet inspection and on-path spoofing, yet standard DoT and DoH merely transfer full domain browsing histories from residential carriers to upstream resolver operators. Achieving genuine network anti-tracking requires decoupling client IP identity from query payloads via Oblivious DoH or Anonymized DNSCrypt, sealing TLS handshakes with Encrypted Client Hello, and isolating sensitive wallet RPC traffic.</summary>
  </entry>
  <entry>
    <title>Hardened Mobile Operating Systems &amp; Anti-Fingerprinting Browsers: 2026 Security Matrix</title>
    <id>https://dt.gl/privacy/hardened-os-browsers</id>
    <link href="https://dt.gl/privacy/hardened-os-browsers" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Operating system and browser hardening must address both commercial telemetry harvesting and zero-click memory-corruption exploits. In 2026 evaluations, GrapheneOS on Armv9 hardware leads mobile exploit defense via hardware Memory Tagging Extension, hardened_malloc, and unprivileged Sandboxed Google Play, while Mullvad Browser and Brave enforce opposing crowd-uniformity versus per-session randomization defenses against high-entropy browser fingerprinting.</summary>
  </entry>
  <entry>
    <title>Hardware Security Keys (FIDO2 / WebAuthn prf) &amp; Agentic MCP Security: 2026 Engineering Guide</title>
    <id>https://dt.gl/privacy/hardware-keys-and-mcp-security</id>
    <link href="https://dt.gl/privacy/hardware-keys-and-mcp-security" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Phishing-resistant authentication and local AI agent security share a single engineering principle: isolating private keys and execution capabilities across hardware-enforced trust boundaries. Hardware FIDO2 security keys bind signatures cryptographically to TLS origins and derive zero-knowledge vault keys via the WebAuthn Level 3 prf extension, while Model Context Protocol servers require digest pinning, Unicode tag sanitization, and rootless container isolation.</summary>
  </entry>
  <entry>
    <title>Encrypted Messaging Protocols &amp; Metadata Resistance: 2026 Cryptographic Audit</title>
    <id>https://dt.gl/privacy/encrypted-messengers</id>
    <link href="https://dt.gl/privacy/encrypted-messengers" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Modern messaging privacy depends equally on post-quantum key ratcheting and metadata graph elimination. In 2026 benchmarks, Signal leads centralized confidentiality via hybrid PQXDH and SPQR ratchets, SimpleX Chat eliminates persistent user identifiers across unidirectional relays, and Briar provides internet-independent Tor, Wi-Fi, and Bluetooth synchronization during state blackouts, whereas Telegram standard cloud chats remain server-readable by default.</summary>
  </entry>
  <entry>
    <title>On-Chain Privacy Protocols, Stealth Addresses &amp; Non-KYC P2P Architecture</title>
    <id>https://dt.gl/crypto-wallets/on-chain-privacy-protocols</id>
    <link href="https://dt.gl/crypto-wallets/on-chain-privacy-protocols" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>On-chain privacy protocols vary fundamentally in anonymity-set topology and regulatory resilience. Heuristic mixing and small-ring decoys degrade under statistical timing and poisoned-output attacks, whereas full-chain zero-knowledge membership proofs such as Monero FCMP++ and Zcash Orchard Halo 2 conceal transaction graphs across millions of shielded commitments while stealth standards like BIP-352 eliminate static address reuse.</summary>
  </entry>
  <entry>
    <title>Major Cryptocurrency Security Incidents and Forensic Post-Mortems (2014-2026 Ledger)</title>
    <id>https://dt.gl/crypto-security/major-incidents</id>
    <link href="https://dt.gl/crypto-security/major-incidents" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Between 2020 and 2026, institutional cryptocurrency losses shifted decisively from simple smart-contract reentrancy bugs toward frontend supply-chain injections, multisig blind-signing payload swaps, cross-chain validator compromises, and off-chain EIP-712 or EIP-7702 signature phishing. Defending treasury and personal custody requires independent calldata verification, deterministic clear signing, strict subresource integrity pinning, and compartmentalized hardware quorums.</summary>
  </entry>
  <entry>
    <title>Post-Quantum Cryptography Engineering Guide: NIST FIPS 203, 204, 205, HQC &amp; Hybrid Migration</title>
    <id>https://dt.gl/privacy/post-quantum-cryptography-fips</id>
    <link href="https://dt.gl/privacy/post-quantum-cryptography-fips" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Cryptographically relevant quantum computers running Shor's algorithm will break RSA, X25519, and ECDSA, exposing recorded classical traffic to Harvest Now, Decrypt Later decryption. NIST finalized FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA), plus selected code-based HQC as a non-lattice backup KEM; engineers should deploy hybrid X25519MLKEM768 key exchange immediately across TLS 1.3, OpenSSH, and file encryption.</summary>
  </entry>
  <entry>
    <title>Crypto Wallets, Silicon Trust Models &amp; RPC Anti-Tracking Engineering</title>
    <id>https://dt.gl/crypto-wallets/self-custody-privacy</id>
    <link href="https://dt.gl/crypto-wallets/self-custody-privacy" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>True cryptocurrency self-custody requires defending two distinct planes simultaneously: private-key extraction resistance on silicon and network metadata isolation on transport. Even an air-gapped hardware signer loses all financial privacy if its companion desktop or browser wallet broadcasts unbatched JSON-RPC balance queries over a residential IP address, linking every derived HD account before a single transaction enters the mempool.</summary>
  </entry>
  <entry>
    <title>DT-INC-2025-001: Bybit $1.46B Safe Multisig UI Supply-Chain &amp; Slot-0 Delegatecall Post-Mortem</title>
    <id>https://dt.gl/incidents/bybit-safe-multisig-2025</id>
    <link href="https://dt.gl/incidents/bybit-safe-multisig-2025" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>On February 21, 2025, DPRK Lazarus Group operators drained 1.46 billion USD in ETH and liquid-staked derivatives from Bybit's Ethereum cold multisig without exploiting any smart contract bug. Compromising a Safe developer workstation allowed attackers to inject targeted AWS S3 frontend JavaScript that tricked three hardware-wallet signers into blind-signing an operation=1 DELEGATECALL overwriting proxy storage slot zero.</summary>
  </entry>
  <entry>
    <title>DT-INC-2025-002: Ethereum Pectra EIP-7702 EOA Sweeper Delegations &amp; Chain-ID Zero Replay Analysis</title>
    <id>https://dt.gl/incidents/eip-7702-sweeper-delegations-2025</id>
    <link href="https://dt.gl/incidents/eip-7702-sweeper-delegations-2025" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Following Ethereum's May 7, 2025 Pectra hard fork, commercial drainer syndicates shifted over 80 percent of malicious delegations to EIP-7702 Type-0x04 SET_CODE authorization tuples. A single off-chain signature over MAGIC byte 0x05 binds an externally owned account's code pointer to 0xef0100 plus a sweeper contract, draining native ETH and multiple ERC-20 tokens atomically and across all EVM chains when chain_id equals zero.</summary>
  </entry>
  <entry>
    <title>DT-INC-2023-009: Ledger Connect Kit NPM &amp; jsDelivr CDN Supply-Chain Injection Post-Mortem</title>
    <id>https://dt.gl/incidents/ledger-connect-kit-supply-chain</id>
    <link href="https://dt.gl/incidents/ledger-connect-kit-supply-chain" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>On December 14, 2023, an attacker used a phished former Ledger employee's unrevoked NPM automation token to publish malicious versions 1.1.5 through 1.1.7 of @ledgerhq/connect-kit containing Angel Drainer. Because Ledger's loader package dynamically fetched unpinned latest JavaScript from jsDelivr CDN without Subresource Integrity hashes, dozens of innocent DeFi frontends served wallet-draining modals simultaneously for nearly five hours.</summary>
  </entry>
  <entry>
    <title>DT-INC-2025-003: Tornado Cash OFAC Sanctions, Fifth Circuit Van Loon Reversal &amp; Immutable ZK Law</title>
    <id>https://dt.gl/incidents/tornado-cash-van-loon-sanctions</id>
    <link href="https://dt.gl/incidents/tornado-cash-van-loon-sanctions" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>On November 26, 2024, the U.S. Court of Appeals for the Fifth Circuit ruled unanimously in Van Loon v. Department of the Treasury that Tornado Cash's immutable Groth16 zero-knowledge pool smart contracts cannot be owned, controlled, or altered by any person and therefore exceed Treasury's statutory property-sanctioning authority under IEEPA, prompting OFAC's formal SDN delisting on March 21, 2025.</summary>
  </entry>
  <entry>
    <title>DT-ADV-2026-001: NIST Selects Code-Based HQC as Fifth Post-Quantum Standard Alongside IR 8547 Deprecation Milestones</title>
    <id>https://dt.gl/advisories#dt-adv-2026-001</id>
    <link href="https://dt.gl/advisories#dt-adv-2026-001" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>NIST selected Hamming Quasi-Cyclic (HQC) from Round 4 candidates as its fifth post-quantum cryptographic standard, providing a code-based Key-Encapsulation Mechanism independent of structured algebraic lattices. ML-KEM (FIPS 203) remains the primary production default across TLS 1.3 and OpenSSH, while HQC establishes cryptanalytic defense-in-depth ahead of NIST IR 8547's 2030 classical deprecation deadline.</summary>
  </entry>
  <entry>
    <title>DT-ADV-2026-002: FTC Final Enforcement Orders Against Gravy Analytics / Venntel &amp; Mobilewalla + California DROP Launch</title>
    <id>https://dt.gl/advisories#dt-adv-2026-002</id>
    <link href="https://dt.gl/advisories#dt-adv-2026-002" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Landmark Federal Trade Commission enforcement orders against Gravy Analytics, its subsidiary Venntel, and Mobilewalla prohibit the unlawful sale of non-consensual mobile advertising SDK location trails and mandate deletion of historic geolocation archives. Paired with California's 2026 Delete Request and Opt-Out Platform (DROP), statutory remedies now reinforce OS-level mobile sensor and ad-ID lockdown.</summary>
  </entry>
  <entry>
    <title>DT-ADV-2026-003: Active Exploitation of Ethereum Pectra EIP-7702 (0x04 SET_CODE) Delegations by Automated Sweeper Contracts</title>
    <id>https://dt.gl/advisories#dt-adv-2026-003</id>
    <link href="https://dt.gl/advisories#dt-adv-2026-003" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Following Ethereum's Pectra upgrade, wallet-drainer syndicates weaponized EIP-7702 type-0x04 SET_CODE authorization tuples to attach persistent malicious smart-contract code (0xef0100 || address) directly onto victim Externally Owned Accounts. Signing a single off-chain authorization with chain_id = 0 allows attackers to sweep ETH and ERC-20 deposits automatically across every EVM chain simultaneously.</summary>
  </entry>
  <entry>
    <title>DT-ADV-2026-004: CalyxOS v7.2.2.0 Production Relaunch Under Open-Source HSM Code-Signing Governance</title>
    <id>https://dt.gl/advisories#dt-adv-2026-004</id>
    <link href="https://dt.gl/advisories#dt-adv-2026-004" />
    <updated>2026-11-11T00:00:00Z</updated>
    <summary>Following a multi-month OTA freeze triggered by 2025 leadership transitions at the Calyx Institute, CalyxOS resumed production builds in July 2026 with version 7.2.2.0 (Android 16) signed by a newly provisioned open-source Hardware Security Module (HSM) infrastructure. Legacy pre-pause installations require verified key-lineage migration, while GrapheneOS retains exclusive Armv9 MTE memory hardening.</summary>
  </entry>
</feed>
