Normal view
Google Is Testing a Search Bar That Works Outside Chrome
Four groups caught using the same Chrome and Windows exploit kit
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.


Β© Getty Images
Chrome moves a step closer to an official Flatpak
If youβve installed Chromium or Google Chrome as a Flatpak, youβve installed an unofficial, community-maintained package done independently of the search giant β that could be about to change. Chromiumβs build system is now able to generate Flatpak packages of the browser itself, though its developers caution that the change does not mean official Flatpak support is coming. A commit made by Googleβs Tom Anderson this week adds the necessary packaging scripts and a build flag (enable_flatpak) to produce a .flatpak package rather than a .deb or .rpm, but that flag is off by default (for now). If enabled, Googleβs [β¦]
You're reading Chrome moves a step closer to an official Flatpak, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.
Chrome moves a step closer to an official Flatpak
If youβve installed Chromium or Google Chrome as a Flatpak, youβve installed an unofficial, community-maintained package done independently of the search giant β that could be about to change. Chromiumβs build system is now able to generate Flatpak packages of the browser itself, though its developers caution that the change does not mean official Flatpak support is coming. A commit made by Googleβs Tom Anderson this week adds the necessary packaging scripts and a build flag (enable_flatpak) to produce a .flatpak package rather than a .deb or .rpm, but that flag is off by default (for now). If enabled, Googleβs [β¦]
You're reading Chrome moves a step closer to an official Flatpak, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.
Google Chrome arrives on Arm64 Linux, Widevine DRM included
Google Chrome now has an official Arm64 Linux build, including for the Raspberry Pi, available via Google's Debian and RPM repos with Widevine DRM support.
You're reading Google Chrome arrives on Arm64 Linux, Widevine DRM included, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.
Google Chrome arrives on Arm64 Linux, Widevine DRM included
Google Chrome now has an official Arm64 Linux build, including for the Raspberry Pi, available via Google's Debian and RPM repos with Widevine DRM support.
You're reading Google Chrome arrives on Arm64 Linux, Widevine DRM included, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.