GPT4Free Privacy Risks Expose AI Prompts to Third-Party Servers and Hidden Logs
Gen Digital researchers found GPT4Free's hosted chat routes prompts through third-party servers, mislabels models, and logs IPs and conversations for up to 30 days.
Gen Digital researchers tested the GPT4Free (G4F) hosted chat at g4f.dev and found requests routed through intermediary endpoints such as an OpenAI-compatible g4f.space endpoint before reaching providers like Google Gemini, sometimes returning different model identifiers such as gemini-3-flash-preview. Provider code referenced JSON files listing over 200 externally reachable Ollama and llama.cpp endpoints whose ownership and authorization were undisclosed. Code paths reportedly retain usage logs for 14 days (IP addresses, approximate geolocation, provider, model, conversation data) and error logs for 30 days, while Privacy Policy and Terms of Service links redirected to a member area instead of the documents.
ASLEval: Measuring Privacy Exposure Displacement in LLM Agent Sessions
ASLEval benchmark shows local privacy proxies miss 46.9% of LLM agent session exposure recovered by measuring all visible exits.
Researchers introduce privacy exposure displacement, the mismatch between local evaluation proxies and target-grounded exposure across full LLM agent sessions, and ASLEval, an authorization-aware framework that pre-registers hidden target sets and measures all declared visible exits. Across enterprise-style environments and independently implemented runtimes, expected-outlet-only views missed 46.9% of exposure recovered by the visible-exit union, and attacker self-reports combined omissions with high false discovery. Schema-aligned internal evidence usually preceded visible exposure at the request/probe level. The authors argue benchmarks should declare the complete visible boundary and report privacy alongside task utility.
Privacy Failure in Split-LLM Training, The Returned Gradient Nullifies the Decoys
Researchers show split-LLM training leaks privacy via zero-valued gradients on decoy rows, exposing which activations are real despite passing forward-channel checks.
A systems-security case study of a two-node split-LLM training setup found that the returned output gradient from an Untrusted Cloud Node is exactly zero for decoy rows, revealing which rows are real. Across nine seeds, zero patterns identified real rows in 4,096 of 4,096 frames per run, and an attack on frame contents recovered 0.65 to 1.50 percentage points of extra tokens over a baseline. Both datasets passed forward-channel privacy and quality checks but failed once the returned gradient was included. Row-wise gradient clipping and noise closed the leak for roughly 0.01 nats of held-out cross-entropy, though five unmeasured attack classes remain.
Inside ‘Project Lily’: The Humans Reading Your ChatGPT Chats
404 Media reveals OpenAI's 'Project Lily' has hundreds of contractors reading real ChatGPT user prompts, exposing sensitive personal data despite privacy filters.
404 Media reports that OpenAI employs hundreds of contractors who read real ChatGPT user prompts, including whole conversations, to rate and critique the chatbot's responses across a user base of over 900 million. Prompts are anonymized and run through OpenAI's Privacy Filter model, but the company acknowledged sensitive personal details can still reach reviewers, and 'user memories summaries' may reveal a user's location and personal context. The review work includes training ChatGPT to be less sycophantic and to stop anthropomorphizing itself, following lawsuits linking the sycophantic 4o model to multiple suicides. Anthropic confirmed it also uses human review to improve its models, and OpenAI's 'improve the model for everyone' data-sharing setting is on by default for free, Plus, and Pro users.
Watch out: Apple timepiece can grab snippets of conversation without both speakers' consent
Apple's Watch Series 12 Live Rewind and Siri Recap transcribe nearby conversations without bystander consent, drawing EFF criticism over all-party-consent laws.
Apple Watch Series 12's Audio Intelligence features on the S11 chip include Live Rewind, which transcribes the last 15 seconds of a conversation after a Digital Crown double-press, processing audio in a Secure Exclave and routing it to a nearby iPhone. Siri Recap generates AI summaries of daily conversations without retaining raw audio or attributing speakers. Apple says an audible chime and visual cue alert bystanders, but privacy advocates including the EFF note that 11 US states require all-party consent for recording and that bystanders have no practical way to opt in or decline.
The Illusion of Local Privacy: Confidentiality Boundary Failures in Consumer LLM Serving Systems
Researchers show local LLM serving systems leak prompts via memory residue, plaintext persistence, a llama.cpp tenant-isolation flaw, and timing oracles.
A study of consumer local-LLM serving systems identifies four boundaries where prompt confidentiality fails: model loading, runtime memory, wrapper persistence, and the serving interface. Using the LLAnalyzer framework across four open-weight model families and two deployment platforms, the authors recover plaintext prompts from allocator-managed memory after inference and show wrappers extend prompt lifetime. They also uncover a previously undocumented llama.cpp authorization flaw letting one authenticated client restore another tenant's saved conversation state, succeeding in 200/200 trials, plus a remote timing oracle via shared prompt-prefix caching that works over WAN.
How to Secure Enterprise AI: From Adoption to Incident Readiness
Sygnia-backed guidance urges a lifecycle approach to enterprise AI security, citing survey data that AI adoption is outpacing governance and incident readiness.
The Hacker News published Sygnia-sponsored guidance on securing enterprise AI across its lifecycle, from use-case definition and vendor selection to deployment and incident readiness. It cites Sygnia's 2026 CISO survey of 600 senior leaders: 63% expect AI fully embedded by 2027, 73% say their organization would not be fully ready for a significant cyberattack, and 67% of executives believe unapproved AI tools already caused a breach. The piece highlights shadow AI, ad hoc integrations, and over-permissioned AI agents as key attack surface risks, noting only 38% of organizations report a comprehensive AI policy.
OpenAI previews privacy-focused system for detecting AI misuse
OpenAI previews Private Safety Processing, detecting cross-interaction AI misuse without exposing customer prompt content, rolling out in September.
OpenAI previewed Private Safety Processing for API and enterprise customers, a system that analyzes patterns across related interactions to flag potential misuse while restricting OpenAI personnel from accessing underlying content. It builds on Zero Data Retention (ZDR) deployments, keeping content on customer-controlled infrastructure or a planned option using customer-controlled encryption keys, with prompts and responses not retained after processing. A technical white paper and rollout are planned for September; images flagged as potential CSAM are the retention exception.
From Hacks to Bioweapons, Claude Misuse Is Now Everywhere
Anthropic reports Claude was misused by Midnight Blizzard, ShinyHunters, disinformation campaigns, and bioweapon attempts; roundup also covers Xinbi takedown.
Anthropic's new report documents eight months of Claude misuse: Russian state-sponsored hackers (Microsoft-named Midnight Blizzard) used it for reconnaissance against Ukrainian and European government networks, stealing data and maintaining access, while ShinyHunters used it across hacking and extortion campaigns, and users attempted bioweapon development. Anthropic says it disrupted the activity. The WIRED roundup also covers the US seizure and sanctioning of Xinbi Guarantee, a Telegram black market with $30 billion-plus in sales mostly laundering pig-butchering scam proceeds, plus DOJ raids on 13 scam compounds in Madagascar and a four-year prison sentence for a Conti ransomware member. Meta faces scrutiny over AI child abuse ads and a class action over photo harvesting for AI training.
ChatGPT’s new feature could give infostealers a map of your Mac activity
OpenAI's Computer History feature for macOS ChatGPT logs app and website activity into memories, raising prompt injection and infostealer privacy risks.
OpenAI's Computer History builds timelines of Mac activity from interaction events and macOS accessibility data, turning them into memories for ChatGPT and Codex. The feature is opt-in, requires Memories, runs only in the ChatGPT macOS desktop app, and is unavailable in the EEA, Switzerland, and the UK. Raw event files stay on-device and are deleted after 48 hours, but generated Markdown memory files are unencrypted and persist until manually deleted. OpenAI itself flagged unencrypted files and prompt injection risks, and security experts warned infostealers could use the logs as a ready-made map of someone's workday.
Meta AI builds detailed profiles of children from years of family posts
Meta AI suggested questions about a child and assembled detailed family profiles from years of Facebook posts, including a photo deleted years ago.
A mother reported that Meta AI on Facebook suggested the question 'Who is the child passenger?' and then aggregated her children's names, birth dates, videos, and a photo she had deleted years ago. The assistant also pieced together old posts to pinpoint her home location when prompted with 'Where does Kalie Robins live?'. Meta admitted the prompt 'never should have' appeared and said it fixed the suggestion issue, while noting the data came from posts the asker could already access. The article situates this among prior Meta AI privacy failures, including publicly shared chats and a bug exposing private conversations via guessable IDs.
CounterPersona: Append-Only Defense Against Unauthorized Persona Skill Distillation
CounterPersona appends targeted counter-persona evidence after data collection to block AI systems from distilling an individual's behavioral patterns into reusable skills.
CounterPersona defends against unauthorized persona skill distillation, where attackers extract recurring patterns from collected personal data to replicate an individual's behavior. Unlike perturbation-based defenses that require modifying data before collection, it works in an append-only setting where historical records cannot be altered or revoked. It constructs targeted counter-persona evidence, packs compatible behavioral states into compact realization units, and strengthens them via rationale-guided consistency rewriting. Experiments show strong effectiveness across lexical, semantic, and LLM-based measures, remaining robust across different distillers.
10 most critical LLM vulnerabilities
OWASP updated its Top 10 LLM application vulnerabilities, ranking prompt injection first and elevating excessive agency to third amid agentic adoption.
OWASP refreshed its Top 10 list of critical vulnerabilities in LLM applications, for the first time incorporating real-world incident data alongside expert voting. Prompt injection and sensitive information disclosure remain first and second, while excessive agency jumped from sixth to third as agentic systems that call APIs and execute code proliferate. Unbounded consumption of AI resources rose in prominence, while improper output handling dropped to the bottom as output sanitization becomes widespread. The list includes remediation guidance such as strict output schemas, human-in-the-loop approvals, and least-privilege credentials held in application code.
Project noRecognition: Teaching AI to Fool Surveillance Cameras
Security researcher Bill Swearingen's noRecognition project uses 31 million tested patterns to defeat license plate reader and surveillance camera AI detection.
Kansas City researcher Bill Swearingen built noRecognition, using reinforcement learning across roughly 31 million tests to generate printed patterns that break the detection layer of license plate readers and surveillance cameras. The strongest validated result achieved 61.7% non-detection against a detector taken from a real deployed camera, though most headline figures remain digital simulations. At DEF CON he covered a 2009 Toyota Yaris in a new pattern and reported it effective against a Flock Safety camera, with curved wheels the main weak point. He is crowdfunding apparel products and withholding his best patterns to prevent camera makers from blocking them.
LLMs and Contextual Integrity
Bruce Schneier highlights two papers: the CIMemories benchmark shows frontier LLMs leak memory attributes up to 69%, and an RL method reduces inappropriate disclosures.
Bruce Schneier discusses contextual integrity in LLMs, referencing the CIMemories benchmark, which uses synthetic profiles with 100+ attributes per user to test whether models with persistent memory disclose sensitive information appropriately. Evaluation showed frontier models exhibit up to 69% attribute-level violations, with GPT-5's violation rate rising from 0.1% to 9.6% across 40 tasks and reaching 25.1% with repeated prompting, showing unstable leakage behavior. A second paper introduces a reinforcement learning framework trained on a synthetic 700-example dataset that substantially reduces inappropriate disclosure while maintaining task performance, with improvements transferring to the human-annotated PrivacyLens benchmark.
OpenAI, Anthropic, Google API Flaw Let Weaker AI Models Decode Stronger Models' Reasoning
Researchers show encrypted reasoning blocks in OpenAI, Anthropic, and Google APIs can be replayed to recover hidden reasoning and secrets like API keys.
Researchers demonstrated that encrypted reasoning objects from OpenAI, Anthropic, and Google reasoning APIs could be replayed across sessions, users, and models, letting weaker same-family models act as decoders of hidden reasoning. Across 6,708 public agent trajectories they decoded 315,320 thinking blocks and found 704 privacy artifacts from real user sessions, including 62 API keys, 33 passwords, 24 access tokens, and seven private keys. The replayable blocks also enabled invisible prompt-injection proof-of-concepts; the main extraction attack is no longer reproducible as of August 2026 following mitigations, though no vendor has publicly acknowledged the flaw.