AntiMalwareSeptember 15, 2026🇷🇺Translated from Russian

WordPress to Automatically Block High-Risk Plugin Updates Before Distribution

WordPress is launching an automated security check for every new plugin release before it is distributed through the WordPress.org API. High-risk updates will be blocked automatically, preventing millions of sites from installing problematic code by clicking "Update."

Previously, the WordPress team reviewed new plugins only at the initial submission stage. Subsequent versions were released without mandatory security screening, allowing a previously safe plugin to later introduce vulnerabilities, backdoors, or changes in ownership with malicious intent.

Under the Protect The Shire initiative, every release now faces a mandatory six-hour delay. During this period, multiple AI models together with Jetpack Scan analyze the code changes. Their findings are combined into a final risk rating.

If the rating is high, the update is excluded from automatic installation. Developers receive an email detailing the detected issues. The mechanism already demonstrated its value before full deployment: on 28 July it identified a backdoor in an unnamed plugin with approximately 20,000 active installations. The release was still in the waiting period and never reached sites. Within 26 minutes of a Wordfence notification, the plugin was closed for downloads.

A high risk score does not automatically imply malicious intent. The system treats both deliberately inserted malware and accidental dangerous errors with equal seriousness. Developers are invited to review the findings, fix the code, and release a new version. If the new version passes the threshold, it proceeds to distribution. Results can be appealed, but WordPress notes that correcting the release is typically faster than awaiting manual review.

Related articles

HispasecSupply Chain & Open Source

Twitch Enhanced Viewer Extension Leaks OAuth Tokens From Nearly 31,000 Users

The browser extension Twitch Enhanced Viewer | JeetBot, available in the official Chrome Web Store and Mozilla Add-ons, secretly forwarded OAuth session tokens to proxies controlled by its operator. These bearer tokens allow full account takeover without passwords or second-factor authentication, enabling actions such as reading and sending whispers, posting in chat, and modifying account settings. The issue surfaced prominently in the v85.x branch where tokens were appended as the &auth= query parameter during network redirects to operator-controlled proxy servers, exposing them in clear text within proxy logs. Earlier v4.x versions had already transmitted tokens via POST requests to a set-token endpoint and backup servers on deno.dev and deno.net. A fix appeared in Firefox version 85.8.7 that stops token exfiltration by altering playlist retrieval, while a Chrome patch is in preparation. Users are advised to uninstall the extension immediately, revoke all active Twitch sessions, and review recent account activity for signs of unauthorized use.

HispasecSupply Chain & Open Source

Twitch Enhanced Viewer Extension Leaks OAuth Tokens from Nearly 31,000 Users

The browser extension Twitch Enhanced Viewer | JeetBot, available in the official Chrome Web Store and Mozilla Add-ons, secretly forwarded OAuth session tokens to proxies controlled by its operator. These bearer tokens allow full account takeover without passwords or second-factor authentication, enabling actions such as reading and sending whispers, posting in chat, and modifying account settings. The issue became especially severe in the v85.x branch, where tokens were appended as the &auth= query parameter during network redirects to the operator’s proxy servers, exposing them in clear text within proxy logs. Earlier versions had already transmitted tokens via POST requests to a set-token endpoint and maintained backup endpoints on deno.dev and deno.net. A fix is available in Firefox starting with version 85.8.7, which stops token exfiltration by changing the playlist retrieval method, while a corresponding Chrome patch is in preparation. Users are advised to uninstall the extension immediately, revoke all active Twitch sessions, and review recent account activity for signs of unauthorized use.

安全客Supply Chain & Open Source

Widespread AI Outage Exposes Fragile Cloud Dependencies Behind ChatGPT, Claude and Grok

On September 3, major AI services including ChatGPT, Claude, Grok, Copilot and Gemini suffered a simultaneous outage lasting nearly four hours. The incident began around 9:30 a.m. ET with ChatGPT and rapidly spread, generating over 12,000 reports on Downdetector within twenty minutes. Industry analysis points to underlying cloud infrastructure rather than the models themselves, with Microsoft Azure and Cloudflare identified as the most likely points of failure. Developers relying on tools such as Cursor experienced immediate loss of code completion and intelligent assistance, forcing manual workflows. The event highlighted single points of failure created by heavy concentration of AI workloads on a small number of cloud providers. Security professionals are urged to map AI supply chains, prepare fallback procedures, monitor infrastructure status pages and adopt multi-vendor routing for critical operations.

HabrSupply Chain & Open Source

Protestware: How Ideologically Motivated Attackers Compromise Open Source Code and Supply Chains

Protestware represents a growing supply chain risk where open source maintainers deliberately insert destructive or politically motivated code into widely used packages. Unlike traditional malware seeking financial gain, protestware is driven by ideological motives and can delete files, cause denial of service, or restrict functionality based on geography or locale. Notable incidents include the node-ipc and peacenotwar packages that overwrote files on systems in Russia and Belarus, the colors.js infinite loop causing DoS, and es5-ext triggering high CPU usage during specific hours or Russian locales. These attacks often hide in postinstall hooks, use geolocation checks via ipinfo.io, or activate via environment variables and timestamps. Detection requires static analysis for geo-IP logic, dynamic monitoring in sandboxes, and tools such as Software Bill of Materials and OpenSSF Scorecard. Organizations are advised to adopt Zero Trust for dependencies, pin versions, use internal artifact repositories, and follow frameworks including NIST SSDF and SLSA to mitigate risks.