❌

Normal view

Four groups caught using the same Chrome and Windows exploit kit

9 September 2026 at 21:55

A nearly identical exploit kit that targets critical vulnerabilities in both Chromium-based browsers and older versions of Windows is being actively used by at least four hacking groups, some of which have ties to the Chinese government.

Researchers from security firm Proofpoint said Wednesday that BlueMoon, the name they gave to the kit, chains three vulnerabilities together so the attackers using it can install malware of their choice. BlueMoon exploits two Chromium vulnerabilities and one in the kernel of Windows 10 (Oct. 2018 Update), Windows Server 2019, Windows 10 2004, Windows Server 2022, and the initial release of Windows 11. All three vulnerabilities have received patches in the past 24 hours.

Deployed rapidly, widely shared

The attacks lacked the stealth found in many campaigns. More often, hackers want to exploit newly discovered vulnerabilities sparingly to lengthen their longevity. Proofpoint hypothesized that one reason for the widely used and visible exploit chain was to take advantage of a “patch gap” in the Chromium supply chain, which spans the time a patch is available from developers and the time that patch is incorporated into browsers such as Chrome and Edge. Another likely contributor was the use of AI, which can often spot vulnerabilities faster than discovery performed solely by humans.

Read full article

Comments

© Getty Images

4 groups caught using the same Chrome and Windows exploit kit

9 September 2026 at 21:55

A nearly identical exploit kit that targets critical vulnerabilities in both Chromium-based browsers and older versions of Windows is being actively used by at least four hacking groups, some of which have ties to the Chinese government.

Researchers from security firm Proofpoint said Wednesday that BlueMoon, the name they gave to the kit, chains three vulnerabilities together so the attackers using it can install malware of their choice. BlueMoon exploits two Chromium vulnerabilities and one in the kernel of Windows 10 (Oct 2018 Update), Windows Server 2019, Windows 10 2004, Windows Server 2022, and the initial release of Windows 11. All three vulnerabilities have received patches in the past 24 hours.

Deployed rapidly, widely shared

The attacks lacked the stealth found in many campaigns. More often, hackers want to exploit newly discovered vulnerabilities sparingly to lengthen their longevity. Proofpoint hypothesized that one reason for the widely used and visible exploit chain was to take advantage of a “patch gap” in the Chromium supply chain, which spans the time a patch is available from developers and the time that patch is incorporated into browsers such as Chrome and Edge. Another likely contributor was the use of AI, which can often spot vulnerabilities faster than discovery performed solely by humans.

Read full article

Comments

© Getty Images

Google Chrome will now ship security updates every two weeks, thanks to AI

9 September 2026 at 11:00
  • Chrome will get new updates every two weeks to minimize real-world attacks
  • Smaller, incremental changes should also make it easier to track any issues
  • Other major browsers are also shifting to two-weekly release cycles

Google has confirmed that Chrome has officially moved from a four-week Stable release cycle to a two-week one, with effect from September 8 2026 with the launch of Chrome 153.

Besides adding new features, the main objective is for Google to give us performance and security fixes more promptly in an era of increased complexity and heightened vulnerabilities.

And it's exactly those security concerns that pushed Google to want to double Chrome's update frequency in the first lace, with the company now having to deal with a higher volume of patches than ever before.

Chrome will get updates every two weeks

Together with a higher volume of attacks in general, Google has also benefitted from AI-powered vulnerability discovery tools, giving developers more work to do than before. "With automated AI discovery tools and community bug reports generating higher patch volume, shorter release cycles make managing security fixes significantly simpler," the company wrote.

Crucially, the faster cycle reduces the time between a fix landing in Chrome's public codebase and it actually reaching end users, making it less likely for a bug to be exploited in the wild.

Chrome has been adhering to a four-week cycle since 2021, but the world is a very different place in the space of just half a decade.

With the higher pace of releases, Google also anticipates a smaller scope of changes, which could actually be a good thing because it could be easier for developers to identify what went wrong in the event of any issues.

Desktop, Android and iOS versions of Chrome will all be impacted by the change, with Chrome 154 already slated for a September 22 release.

More broadly, Google says Chrome isn't the only browser getting more frequent updates. Microsoft, Mozilla and Brave are also making similar changes, and they're all undergoing those changes right now.

Google logo on a black background next to text reading 'Click to follow TechRadar'

MacVoices #26168: Road to Macstock – Mike T. Rose

By: Chuck
4 June 2026 at 16:36
The Road to Macstock takes a serious turn as Mike T. Rose previews his workshop on becoming a digital caretaker for family members and loved ones. Mike discusses scams targeting older adults, password sharing, remote support, Apple Passwords, financial preparedness, and the need to balance protection, respect, independence, and trust when helping others manage their digital lives. 

💾

MacVoices #26158: Live – A Fake Vendor Site, Vision Pro, Apple Reorg, and the Impact of the Neo

By: Chuck
28 May 2026 at 21:34
The MacVoices Live! panel covers a fake vendor site spreading malware, Apple’s new accessibility previews, and a hardware reorganization aimed at faster, more unified product development. Chuck Joiner, David Ginsburg, Eric Bolden, Web Bixby, Jim Rea, Brian Flanigan-Arthurs, Jeff Gamet, and Marty Jencius also discuss Eyes Off for shoulder-surfing protection, Microsoft and Google reactions to the MacBook Neo, Google’s proposed AI laptop, and broader questions about AI becoming part of operating systems. 

💾

MacVoices #26154: Live! – The Steve Jobs Coin, The MacBook Neo, A Wide-Reaching Hack, and Digg’s Return…Again

By: Chuck
26 May 2026 at 20:23
A wide range of tech stories get the MacVoices treatment, starting with the quick sellout of the Steve Jobs commemorative coin and what strong MacBook Neo demand may say about Apple’s pricing, chip planning, and enterprise appeal. Chuck Joiner, David Ginsburg, Marty Jencius, Eric Bolden, Brian Flanigan-Arthurs, Jeff Gamet and Mark Fuccio also discuss Apple updates unexpectedly changing settings, a Canvas ransomware disruption affecting schools, Chrome’s hidden AI download, Google’s Liquid Glass similarities, Digg’s AI-focused return, and safer lithium coin batteries. 

💾

Como mostrar as legendas do Gemini Live no Google Chrome [Mac]

15 August 2026 at 19:00

O Chrome traz vários recursos de integração com outros serviços do Google, como é o caso do Gemini — solução de inteligência artificial da empresa.

O Gemini Live permite manter conversas ininterruptas com a IA, como se fosse uma conversa com outra pessoa.

Para quem possui surdez ou alguma dificuldade de audição, é possível habilitar a exibição das legendas do Gemini Live enquanto estiver usando-o no seu Mac. Veja como! 👨‍💻

Com o app aberto, acesse as configurações do navegador. É possível fazer isso indo até Chrome » Ajustes…, na barra de menus, usando o atalho de teclado ⌘ command , ou clicando no botão com três pontinhos (no canto superior direito).

Selecione “Inovações de IA” (na barra lateral esquerda) e entre em “Gemini no Chrome”.

Por fim, marque a chave ao lado de “Legenda descritiva”.

Na prática, você poderá conferir as legendas nas conversas do Gemini Live, como no exemplo abaixo:

Muito bacana, não acha? 😉

Como alterar a posição do painel lateral do Gemini no Google Chrome [Mac]

15 August 2026 at 17:30

Com a disponibilização do Gemini no Google Chrome para Macs, ficou muito fácil consultar o serviço de inteligência artificial da empresa para alguma atividade que precisa fazer.

Por padrão, o painel lateral do Gemini fica localizado na parte direita da tela do seu computador. Mas, se preferir, é possível que ele seja mostrado no lado esquerdo.

Veja como escolher isso! ✨

Acesse as configurações do Chrome usando um dos seguintes métodos:

  • Vá até Chrome » Ajustes…, na barra de menus;
  • Use o atalho de teclado ⌘ command ,;
  • Clique nos três pontinhos (no canto superior direito) e em “Configurações”.

Depois, acesse “Aparência” (na barra lateral esquerda).

Na seção “Posição do painel lateral”, use o menu suspenso “Gemini” para escolher entre “À direita” ou “À esquerda”.

Como mudar o atalho de teclado do Gemini no Google Chrome para Mac

15 August 2026 at 16:00

Com a liberação do Google Gemini no navegador Chrome para macOS, tornou-se possível utilizar a inteligência artificial da empresa de uma maneira rápida, sem precisar abrir um aplicativo separado, por exemplo.

Uma das maneiras de sair ou voltar a navegar pelo Gemini no Chrome é por meio de um atalho de teclado. Apesar de já vir com um pré-configurado, você pode alterá-lo.

Veja como! 😉

Abra as configurações do Chrome, indo até Chrome » Ajustes…, na barra de menus, usando o atalho ⌘ command , ou clicando nos três pontinhos, no canto superior direito.

Selecione “Inovações de IA” e entre em “Gemini no Chrome”. Clique no lápis ao lado de “Atalho para navegação” e utilize o teclado para adicionar o novo atalho preferido.

Como desativar o botão do Gemini no Google Chrome do Mac

15 August 2026 at 14:30

Recentemente, o Google atualizou o navegador Chrome para incluir recursos de inteligência artificial do Gemini.

Porém, uma novidade que certamente não agradou muita gente foi a presença de um botão dedicado à IA no canto superior direito do browser no macOS.

Felizmente, usando um truque bem simples, é possível ocultá-lo. Veja como! 😉

Com o Chrome aberto no Mac, abra os ajustes do navegador usando um dos seguintes métodos:

  • Vá até Chrome » Ajustes…, na barra de menus.
  • Use o atalho ⌘ command ;.
  • Clique nos três pontinhos (ao lado da sua foto, no canto superior direito).

Depois, clique em “Inovações de IA” (na barra lateral esquerda) e entre em “Gemini no Chrome”.

Por fim, desmarque a opção “Mostrar o Gemini na parte de cima do navegador”.

Google Should Still Be Forced To Shed Chrome, Advocacy Group Argues

9 August 2026 at 04:52
"Google should be required to divest the Chrome browser, and prohibited from paying Apple to distribute Google's search engine, the nonprofit advocacy group Public Knowledge argues in a new court filing," MediaPost reports, citing a friend-of-the-court brief filed Tuesday in the D.C. Circuit Court of Appeals: The group adds that "independent ownership" of Chrome "would open the distribution channel Google controls and allow Chrome to serve browser users when it makes privacy decisions and determines how to integrate search and (artificial intelligence)..." In September 2025, [U.S. District Court Judge] Mehta issued a remedies order that requires Google to share some data about users' searches with "qualified" competitors and to provide syndicated search results and ads to those competitors. The order also prohibits Google from entering into exclusive distribution contracts for Google Search, Chrome, Google Assistant and the Gemini app for six years, but allows the company to continue to make payments for search-ad revenue or distribution to Apple, Mozilla and others... Google recently appealed Mehta's order. The company argued in its written brief that it "prevailed in the marketplace fair and square," adding that Apple and Mozilla "sensibly chose" Google as the default search engine "because it gave their users the best experience," and because Apple and Mozilla would earn the most ad revenue through the deals. The [U.S.] Justice Department and states countered to the appellate court last week that the liability finding should stand, and also argued that Google should have been banned from paying Apple and Mozilla for placement as the default search engine on their browsers. [Antitrust enforcers had originally asked the judge to order Google to divest Chrome, but he's already rejected that request.] The government did not argue in its appellate papers that Google should be forced to sell Chrome. But Public Knowledge independently contends in its friend-of-the-court brief that divestiture would benefit consumers... "Divestiture would place those decisions with an institution whose success depends on serving browser users primarily...." The group is calling the appellate court's attention to Google's April 2025 decision to preserve tracking cookies — a reversal from its earlier plans to block third-party cookies by default. "Google is in the position of both deciding Chrome's tracking rules while running the advertising business affected by them," Public Knowledge writes. "An independent Chrome could make those decisions on behalf of users alone." But Firefox developer Mozilla filed its own friend-of-the-court brief Thursday warning Firefox could be forced to "exit the browser and browser engine markets" if it can't receive payment from Google for distributing its search engine, according to a later report from MediaPost: Federal and state antitrust enforcers recently asked the appellate court to reverse the portion of Mehta's order that allows those payments to continue. But Mozilla counters in its new friend-of-the-court brief that Mehta's decision regarding those payments was supported by the evidence --including a study it conducted concluding that its revenue would "decline dramatically" if forced to replace Google with Bing as Firefox's default search engine... Google is expected to file new arguments with the appellate court next month.

Read more of this story at Slashdot.

Dropping Manifest V2 Extensions

30 July 2026 at 20:21

Sayan Sen (Hacker News):

For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.

[…]

Here is a rundown of the changes coming in the final such releases of Chromium releases:

Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024.

Google:

Aug 31st 2026: All remaining Manifest V2 extensions removed from the Chrome Web Store

Previously:

Update (2026-09-02): Web Iterate (Hacker News):

Google today reached the final milestone in a browser-extension transition that has been years in the making, all remaining Manifest V2 extensions were removed from the Chrome Web Store.

Chrome Browser Default at the Top of the Mac App Store

29 July 2026 at 21:45

Jeff Johnson (Mastodon):

Released less than a month ago by an unknown developer, Chrome Browser Default has somehow become a top download in the United States Mac App Store, alongside well-known developers Amazon, WhatsApp/Facebook/Meta, and Microsoft[…]

[…]

Chrome Browser Default is the top search result for “Google Chrome” in the Mac App Store. Chrome itself is distributed as a direct download from Google, outside the Mac App Store. Notice also that the Chrome Browser Default app icon resembles the Google Chrome app icon[…]

Both the name and icon violate Apple’s guidelines, and the preview images are not actually screenshots of the app. The App Store is great for distributing apps that piggyback on the names of popular apps. They’d be hard to find with a regular Web search, but in the App Store they appear at the top.

The app appears to do what the description says it does, though it’s quite primitive and likely vibe-coded. I can add rules, but I couldn’t find a way to edit or delete added rules, which is ridiculous. The developer’s privacy policy is on GitHub in a repository where most of the commits were co-authored by Claude.

[…]

At the bottom is a section that shows, allegedly, what “People are Saying” about the app. Yet none of these 5-star reviews are from the App Store. According to Google Search, the reviews are not from anywhere on the web.

Jeff Johnson:

This app is no longer available in the Mac App Store.

[…]

I have no idea why the Dutch name “Standaard Browser Wisselen” appears in the alert, because the App Store Purchased section says “Chrome Browser Default,” and my only Mac system language is English (US). The name of the developer in the App Store was Chinese, 立花 卢.

[…]

My suspicion is that Apple, not the developer, removed the app from the App Store, which explains why I can’t download it. Whether this removal was triggered by my blog post or by App Store user reports, I don’t know.

Craig Grannell:

Doesn’t say amazing things for the Mac App Store that I find it faster to search for something in a search engine than within the MAS itself. And that’s when I already know the name of what I’m looking for.

Previously:

Google Loses Final EU Antitrust Appeal

23 July 2026 at 20:46

Ryan Whitwam (PDF, Reddit):

Back in 2018, Google was handed a record-setting 4.34 billion-euro ($4.9 billion) fine in Europe for abusing its monopoly on Android. The company has spent the intervening years challenging that decision, but the continent’s highest court has put a stop to that. The Court of Justice of the European Union has affirmed the penalty, meaning Google is out of options.

[…]

The EU took issue with Google search and Chrome being the default options on Android. Even devices made by other companies, such as Samsung and Xiaomi, include Google apps as the default per the Android licensing agreement, giving Google an unfair advantage, according to European antitrust regulators. This is not to be confused with a 2.95 billion euro ($3.45 billion) fine against Google’s advertising monopoly issued by the European Union last year.

Arjun Kharpal:

In 2022, a lower EU court reduced the fine to the current 4.1 billion euros from 4.34 billion euros previously.

Google has argued that the Android operating system provides choice for users and supports developers and businesses across Europe.

Via John Gruber:

Google last year booked $132 billion in profit; this fine is about 3 percent of that..

[…]

There’s never a reason not to string the appeal process out, but it’s especially true when your profits are growing at an exceptional rate. By growing their profits around 5×, they’ve reduced the relative sting of this fine by 5×

Previously:

Google Chrome's Next Update Will Mark the End of Popular Ad Blockers

By: BeauHD
15 June 2026 at 22:00
Google is removing Chrome's last remaining workarounds for Manifest V2 extensions, effectively ending support for legacy ad blockers such as the original uBlock Origin. 9to5Google reports: CyberNews points out a Chromium commit that removes support for the "kExtensionManifestV2Disabled" flag, which is referred to as "dead code" seeing as Chrome no longer supports Manifest V2 extensions. This removal acts as the final stop for many Manifest V2-based ad blocker extensions that were still in use today -- the flag was effectively a loophole to continue using these extensions. A Googler on the commit explains: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire." This will also impact other Chromium-based browsers, though the comment notes that "other browsers can continue supporting these if they so desire." Neowin points out that Microsoft Edge and Opera are likely to follow suit. Chrome 150, set to be released later this month, will remove this flag, while other leftover bits of Manifest V2 will be removed in the v151 release.

Read more of this story at Slashdot.

Google Chrome is closing the loopholes that let old ad blockers keep working

15 June 2026 at 19:06
An image showing the Chrome logo surrounded by yellow circles

Google Chrome version 150 and 151, expected in late June and July, respectively, will cut off support for the last remaining workarounds for running older ad blockers, 9to5Google reports. Google phased out support for ad-blocking extensions built for Manifest V2, like uBlock Origin, in 2024. At that point, most Chrome users either switched to newer Manifest V3 ad blockers like uBlock Origin Lite or switched to a different browser.

Google is now removing the final bits of code referencing its previous Manifest V2 extensions platform, so only ad blockers that work on the Manifest V3 platform will work in Chrome version 151 onward.

Google d …

Read the full story at The Verge.

Beyond Death | Taxation and an Absolute Limit to Human Lifespan

27 September 2025 at 04:15
According to Benjamin Franklin two things are inevitable: death and taxes. Research shows that human lifespan has a natural limitation, due to the decline of physiological resilience. Contrast the desire of the evil elites to overcome death using barbaric practices with the immortality offered by Jesus Christ.

❌