GitHub Copilot Traffic Analysis via MITM Proxy Exposes Prompt Context Handling and Local SQLite Session Storage
A security researcher conducted an in-depth analysis of GitHub Copilot by routing all network traffic from Visual Studio Code through an mitmproxy instance configured as a man-in-the-middle proxy.
The study began with the observation that Copilot rapidly consumes monthly request quotas, prompting an investigation into its internal communication patterns. Because Visual Studio Code and Copilot are built on Electron, the researcher first mapped the application’s network architecture, distinguishing between Chromium-based renderer processes and Node.js HTTP requests.
Proxy Setup and Traffic Interception
After installing mitmproxy via Homebrew and configuring VS Code proxy settings (Http Proxy, Strict SSL disabled, Proxy Support set to override), the researcher launched mitmweb to capture live requests. Additional steps included restarting the Extension Host process to ensure fresh connections were routed through the proxy.
Traffic analysis showed multiple request categories even before any code was typed: authentication and session management via OAuth, configuration and policy retrieval, MCP registry access, repository and session context, model discovery, and recent repository listings.
Model Intent Routing and Prompt Construction
In Auto mode, Copilot sends each prompt to the /models/session/intent endpoint for classification into categories such as code-gen, debugging, or tool-use. The resulting classification determines which model handles the request.
Inline suggestion requests were observed to include the current file path and content from recently edited files. When a fake secret was placed in a .env file, the secret appeared in prompts generated while editing an unrelated pyproject.toml file, demonstrating that context collection is not limited to the file where suggestions are enabled.
Local Session History and Chronicle Tool
Many requests referenced a tool named session_store_sql that can execute read-only SQLite queries against a local database called session-store.db. The database stores session summaries, user prompts, LLM responses, repositories, branches, and checkpoints.
When the researcher asked Copilot what work had been done the previous week, the model first attempted an invalid query, performed schema introspection, and then successfully retrieved records from the local store using the Copilot Chronicle skill.
The findings illustrate how GitHub Copilot maintains persistent local state and incorporates broad context into prompts sent to remote models.
Related articles
TenetBench Benchmark Tests LLMs for Compliance with Professional Ethical Codes
Researchers from the Institute of Information Security Issues at ISP RAS and the Institute of Cybersecurity and Information Protection at RANEPA have developed TenetBench, a benchmark designed to evaluate how well large language models adhere to specific norms in professional codes of ethics. The benchmark generates realistic work-related prompts that may conflict with rules from documents such as the Code of Professional Ethics for Advocates or journalistic standards on undisclosed advertising. Each test case pairs a conflicting request with a neutral counterpart to measure whether models refuse, warn, or still provide prohibited content. Evaluation separates task completion, norm violation detection, and presence of explicit refusals using an LLM-as-a-Judge approach validated against human annotators. The full dataset contains 3,433 prompt pairs derived from 15 professional codes, with a public subset of 2,235 pairs from 10 documents. Human validation confirmed 99.5% of generated examples as fully plausible work scenarios.
Solar to Showcase Solar AI Firewall for Business Protection Against AI Risks at SOC Forum 2026
GK Solar will present its new Solar AI Firewall solution at SOC Forum 2026 to help organizations control interactions with AI services and prevent confidential data leaks through employee prompts. The product addresses growing risks from staff sending corporate data to neural networks and AI agents gaining access to internal systems. The forum takes place on 27-28 October in Moscow's Lomonosov cluster, with the official launch of Solar AI Firewall scheduled during the event. Solar will also highlight practical risks of AI adoption, including data transmission to external services, use of public models by employees, and new attack surfaces in corporate infrastructure. The solution will be demonstrated as part of an integrated ecosystem for access, network, and data protection. In addition, the company plans to introduce JSOC ONE, a new line of Solar JSOC services tailored for mid-sized businesses that require 24/7 monitoring without building their own SOC.
Researcher Runs 100 Abliterated AI Agents Against His Own Accounts, Achieves Five Successful Breaches
A security researcher deployed roughly 100 autonomous AI agents based on abliterated open-source models to attempt unauthorized access to his online accounts over a five-hour period. The agents successfully compromised three accounts by exploiting vulnerabilities in legacy personal projects and two additional accounts through password reuse and credential stuffing. They also conducted 16 social engineering attempts, harvested and cross-verified personal data from public sources, and generated phishing pages targeting the researcher's Substack and Hacker News presence. Despite these successes, the agents failed to discover any zero-day vulnerabilities in third-party software or gain access to Tier-0 accounts such as Gmail, 1Password, or banking services. The experiment relied on abliterated versions of GLM-5.3 and DeepSeek V4 Flash models running on cloud GPUs, orchestrated via Codex CLI inside Docker containers with access to Railway infrastructure. Total compute cost reached approximately $210, equating to roughly $40 per successful account compromise. The researcher concluded that inexpensive swarms of such agents could soon enable low-skill attackers to systematically map and exploit an individual's entire online footprint.
How Censorship in Closed AI Models Reshapes Science: Hugging Face Releases Open Carbon-X DNA Model
Hugging Face CEO Clement Delangue announced the release of Carbon-X, an open 14.8 billion parameter language model designed for reading, analyzing, and generating DNA sequences. The announcement highlighted how shallow guardrails in closed commercial models blocked even proofreading a tweet discussing the topic. Commenters and researchers pointed out that these input/output filters lack context awareness, blocking legitimate scientific queries while motivated adversaries bypass them through rephrasing. Carbon-X was built on Qwen3-14B with a hybrid BPE and 6-mer tokenizer, domain mid-training on 302 billion tokens, and safety achieved through data curation rather than runtime censorship. The model achieves performance comparable to closed frontier systems at roughly 1/1800th the inference cost for large-scale genomic tasks. The case underscores growing asymmetry between closed corporate AI labs building wet labs and independent researchers restricted by superficial safety layers.