Twitch Enhanced Viewer Extension Leaks OAuth Tokens from Nearly 31,000 Users
The browser extension Twitch Enhanced Viewer | JeetBot, distributed through the official Chrome Web Store and Mozilla Add-ons, forwarded OAuth session tokens to proxies under the control of its operator. With these tokens, an attacker can hijack accounts without needing a password or second factor, allowing actions ranging from reading and sending whispers to writing in chat and altering linked account settings.
The tokens function as bearer credentials: whoever possesses them can operate as the authenticated user. The most critical behavior appeared in the v85.x branch, where the extension added the token as the &auth= query parameter during network-level redirects to the operator’s proxy infrastructure. Because the token traveled inside a URL, it could remain in clear text inside proxy logs, greatly increasing exposure if those logs were accessed or leaked.
The forwarding occurred for nearly every channel a user opened, with the exception of a default list of ten channels. Starting with version 85.8.4, the extension also introduced a Channels with restrictions parameter that gave the appearance of control while the underlying exfiltration continued. Earlier v4.x releases had already sent tokens via POST to a set-token endpoint and maintained backup endpoints hosted on deno.dev and deno.net.
The correction is available in Firefox from version 85.8.7, which eliminates token transmission by altering the playlist retrieval method. The developer stated that an equivalent patch for Chrome is being prepared. Updating or disabling the extension stops further leakage, yet it does not invalidate tokens that have already been sent.
Recommended actions include immediately uninstalling or disabling Twitch Enhanced Viewer | JeetBot, revoking all active Twitch sessions from account settings, forcing re-authentication, and reviewing recent activity, private messages, and chat actions for unauthorized use. In managed environments, organizations should inventory installed extensions, block the affected identifiers pnhhdhhcadcjfckjhpmjneldiegbojfb in Chrome and twitchenhancedviewer@example.com in Firefox, and enforce allow-list policies for corporate browsers.
Related articles
Malicious Code Injected into LiteLLM Open Source AI Package via Supply Chain Attack
The open-source generative AI tool LiteLLM had malicious code inserted into its official distribution packages, enabling credential theft and remote code execution. The compromise affected version 1.107.0 released on October 21, 2026, and was delivered through legitimate channels in a classic software supply chain attack. Seven malicious wheel files were uploaded to PyPI, while official container images on Docker Hub and GitHub Container Registry were also tainted. Security firm JFrog discovered that the malware steals a wide range of secrets including cloud credentials, SSH private keys, browser-stored passwords, development tokens, and AI service API keys from LiteLLM's database. The code also supports execution of externally fetched payloads and abuses Python's startup mechanisms to run even when the application itself is not loaded. This marks the second supply chain incident involving the project in 2026, following a separate event in March.
GhostAction Campaign Compromises 790 GitHub Repositories via Malicious Workflows
Researchers from OpenSourceMalware have identified 790 publicly accessible GitHub repositories containing malicious workflows planted by the GhostAction campaign as of October 9. The campaign abuses trusted maintainer accounts to inject workflows that automatically exfiltrate secrets including AWS access keys and tokens for GitHub, GitLab, Google, Slack, SendGrid, OpenAI, Anthropic, and OpenRouter. Earlier counts by GitGuardian recorded 772 repositories between August 31 and September 30, though the datasets differ and are not cumulative. A separate wave on October 8 impacted 346 repositories linked to two maintainer accounts, including a project belonging to Uber. The malicious workflow runs on code pushes or manual triggers, scans repository files and full Git history for credentials, and sends findings in plaintext to attacker infrastructure. Removing the workflow file does not mitigate exposure, as successful executions already leak credentials and old commits may still contain secrets.
SberTech Launches Platform V Orchestrator for Security Services to Scan Software Before Corporate Deployment
SberTech has announced the launch of a new direction focused on analyzing the security of software prior to its integration into corporate infrastructures. The initiative is built around the company's own Laboratory for Software Verification and the technological platform Platform V Orchestrator for Security Services. This platform combines components for working with both built-in and external analysis tools, enabling checks of digital artifacts, control over software composition and changes, and detection of vulnerabilities, hidden threats, and defects in source code and repositories. SberTech aims to replace fragmented checks and manual result processing with a single managed process, allowing scaled verification without proportional team growth. The move responds to the adoption of hundreds of products from various vendors, widespread use of open-source components, and rising attacks on software supply chains. Primary customers include banks, industrial enterprises, telecom operators, energy companies, and the public sector. The solution is offered as a standalone product that supports on-premises deployment and operation in isolated environments such as private clouds and dedicated data processing contours.
NEC Subcontractor Suffers Cyber Attack Leading to Customer System Disruptions and Personal Data Leak
NEC disclosed that a subcontractor handling system development and maintenance was compromised in a cyber attack during late September 2026. Attackers stole legitimate account credentials and used them to access multiple customer environments from the subcontractor's systems. The intrusion resulted in server files being encrypted, rendering customer systems inoperable. Additional files containing personal information and system details were exfiltrated from a shared cloud storage platform used for coordination between NEC, the subcontractor, and customers. Affected customers have been notified individually, with further details on compromised personal data to be provided as they become available. The incident highlights risks associated with third-party vendor access in IT supply chains.