There is a project on GitHub called Axios. Axios is extremely popular. It is used by millions upon millions of applications. Axios is a programming library that helps your JavaScript code make HTTP/S requests (communicate with websites). In simple terms, if you're a programmer doing something with JavaScript, and want to do stuff that communicates with a website in literally any capacity, people heavily recommend using Axios due to its simplicity. Using Axios you don't have to reinvent the wheel and do a bunch of work. All you need to do is import Axios into your code and you're off to the races. Someone (currently unknown) compromised Axios (currently unknown how) to deliver malware to people. When someone updates or installs Axios, Axios itself contains malware. What the malware does is (currently) unknown, but it is being reversed engineered by probably every malware analyst on the planet at this moment. In a few hours more details will emerge. Information is being exchanged in real time on social media and private communication platforms as I write this. Due to the size and popularity of Axios, it is unknown how many are impacted, it could be millions, it could be thousands, or if we're lucky, only hundreds of people or organizations will be impacted. If this is absolute worst case scenario, millions of organizations across the planet have been infected with malware which (currently) we do not understand. However, the likelihood of this is low. It appears Axios being compromised was detected quickly, potentially within minutes (or hours) of it being compromised to deliver malware. Additionally, the likelihood of every single Axios user updating Axios as soon as it was compromised to deliver malware is astronomically low. It is basically zero. The impact from Axios being compromised is devastating, the fallout from this will be a massive headache. This is unironically a malware nuclear missile and will likely be studied in the future.

New @firefox for Android menu buries extensions deep down into a click pit. But now you can summon your @noscript quicly by sketching a "S" on the web page😎

It couldn't work in the Tor Browser, neither in the @mullvadnet Browser, because of @noscript's noscript.net/usage/#lan-prot… (independent from #JavaScript blocking, which may help as well).

🎉 Tor Browser 15.0 is now available! Our first stable release based on Firefox ESR 140, incorporating a year's worth of changes. Download now from the Tor Browser download page: blog.torproject.org/new-rele…

New, from me and @kellymakena: The FTC is disappearing blog posts about AI that were written during Lina Khan’s tenure as FTC chair wired.com/story/ftc-removes-…

Your WAF can’t see this. Attackers are skimming payment data right now through unmonitored JavaScript—while your dashboards stay clean. The worst part? It’s happening in your customers’ browsers. See what every retailer must fix before Black Friday ↓ thehackernews.com/2025/10/wh…

🚨 CISA Warns of Google Chrome 0-Day Vulnerability Exploited in Attacks Read more: cybersecuritynews.com/cisa-g… CISA has issued a warning about a high-severity zero-day vulnerability in Google Chrome that is being actively exploited in attacks. The vulnerability, tracked as CVE-2025-10585, has been added to CISA’s Known Exploited Vulnerabilities (KEV) catalog, signaling an urgent need for users and administrators to take action. #cybersecuritynews #Vulnerability