Executive Loses $5 Million Golden Parachute After Uploading Documents to DeepSeek
A top manager at a Moscow engineering company attempted to secure five million rubles after her dismissal for disclosing commercial secrets but ultimately lost the case. The court determined that uploading internal documents to DeepSeek was not an acceptable method for obtaining a golden parachute.
The woman had served as sales director for less than six months and received more than 800,000 rubles per month. Following her termination initiated by the employer, she filed a lawsuit to amend the dismissal grounds to mutual agreement and to receive the corresponding five-million-ruble compensation.
The company countered that the employee had repeatedly mishandled confidential data. She forwarded official documents via corporate email while adding her personal address in blind copy. In addition, several files from the company’s internal protected repository were uploaded to the Chinese neural network DeepSeek, which the employer argued created a risk of information interception.
The court found no operational necessity for either sending documents to an email address outside company control or placing them in a third-party AI service. These actions were classified as a gross violation of labor duties and disclosure of commercial and official secrets.
The employer further stated that after confidential information was disclosed during negotiations, one supplier ceased all communication. The company also cited the employee’s systematic failure to meet sales targets.
During proceedings the company proposed a settlement that would change the dismissal wording and pay more than 400,000 rubles, but the former employee rejected the offer in hopes of receiving the full five million. The court dismissed her claims.
The case gained attention following reports that user conversations with DeepSeek had appeared in Google search results, although the ruling did not require proof of an actual leak—only the fact that protected documents had been transferred to an external service.
Related articles
SECURITM Launches MCP Server for External AI Access to Security Data
SECURITM has introduced an MCP server that connects external AI assistants directly to its platform data on assets, risks, tasks, and metrics. This marks the first such implementation among Russian SGRC and SOAR systems. The open MCP protocol enables natural language queries about critical assets without owners, overdue tasks, or monthly metric changes without manual data export. Supported tools include GigaChat, Yandex solutions, Claude, ChatGPT, Cursor, and compatible local models. Access remains strictly read-only through dedicated tokens with optional IP restrictions. The feature is available in paid cloud and on-premise editions and complements the platform’s built-in AI assistant.
One Year Left to Secure Systems as Open-Source GLM-5.3-Flash Enables Automated Cyber Attacks
Chinese company Z.ai Co. released GLM-5.3-Flash in August 2026, an open-weight model that achieves 84.5% on CyberGym and 54.4% on ExploitBench, matching or exceeding leading commercial LLMs in vulnerability discovery and exploitation tasks. The model runs locally on consumer hardware such as a single Nvidia DGX Spark or Apple M5 Mac Studio with 256 GB unified memory, allowing unrestricted use after abliterated versions remove safety alignments. Experts warn that LLM agents could soon scan and exploit zero-days across Windows, Linux, browsers, and messaging apps around the clock. Initiatives Project Glasswing (Anthropic-led) and Daybreak (OpenAI-led) are racing to patch critical vulnerabilities in open-source projects and critical infrastructure before the next generation of unrestricted models arrives. Organizations are advised to accelerate patch deployment, inventory supply chains, and adopt advanced LLMs defensively within the remaining one-year window.
RFC 9421 and Open wbauth Protocol Accelerate AI Agents 5.5x by Replacing Anti-Detect Browsers with Cryptographic Signatures
A new open implementation of the IETF RFC 9421 HTTP Message Signatures standard called wbauth allows AI agents to authenticate using Ed25519 cryptographic signatures instead of resource-heavy anti-detect browser farms. The approach eliminates the need for Camoufox, Playwright, or AdsPower instances that consume 500 MB to 1.5 GB of RAM per process and require residential proxy pools. Benchmarks show cold start time dropping from 1744 ms to 5 ms, request time from 86.8 ms to 15.8 ms, and memory usage from 500 MB to 0.76 MB. The system uses three HTTP headers for signing and verification against a public key directory hosted on Cloudflare Workers and D1. Server-side validation at the WAF or edge involves fetching the public key, canonicalizing the message per RFC 9421, verifying the Ed25519 signature, and checking timestamps to prevent replay attacks. The npm package wb-auth@0.4.0 and PyPI package wbauth-sdk==0.4.0 provide ready-to-use signers for Node, Bun, Deno, Python httpx, and requests. The full source is available on GitHub under the MrKoriy/wbauth repository.
Critical Prompt Injection Flaw in ChatGPT GitHub Connector Allows Theft of Private Repositories
A critical vulnerability in the ChatGPT GitHub connector enables attackers to steal private repositories through indirect prompt injection. Researcher Sunil Tripathy demonstrated that hidden instructions placed in a public GitHub repository can trick the ChatGPT agent into accessing and exfiltrating data from the victim's private repositories. The attack works when the victim connects their GitHub account to ChatGPT with full repository access and then asks the agent to review the attacker's public repo. The injected instructions are executed as trusted commands, allowing the agent to commit malicious GitHub Actions workflows that exfiltrate secrets such as AUDIT_CANARY to attacker-controlled servers. Direct requests to steal data are refused by the agent, but framing the instruction as a deployment requirement bypasses this safeguard. OpenAI's documentation claims the connector is read-only, yet the attack achieves both read and write access across repositories. No CVE was assigned, the report was closed as out of scope on October 14, and the issue remained exploitable on October 15 with no published fix available.