World

CISA has issued a warning about the SafePay ransomware operation, stating that the group has compromised more than 600 critical infrastructure organizations worldwide since 2024.

According to the agency, the campaign has targeted essential services and infrastructure operators across multiple sectors, underscoring the persistent threat ransomware poses to organizations running critical systems.

The advisory highlights SafePay as an active and significant threat, with the reported victim count continuing to grow since the group emerged in 2024.

Source: Unknown

Is your organization reviewing its ransomware defenses in light of this advisory, and if so, what steps are you prioritizing?

ClickFix attacks are surging at an unprecedented scale, with cybercriminals increasingly relying on fake AI tool installers, poisoned search results, and trusted chatbot platforms to convince users into running malware themselves. According to analysis by Push Security, these campaigns are notable for how effectively they bypass traditional security defenses.

The core of the technique relies on social engineering rather than exploitation: victims are walked through pasting a command into a Run dialog or terminal, which fetches and executes the payload. Because the user performs the action voluntarily, conventional protections often fail to flag the activity.

What makes the current wave stand out is the lure. AI tools have become the most convincing pretext yet, with fake installers for popular AI software and malicious search results directing users toward the trap. Attackers are also abusing trusted chatbot platforms to deliver the instructions, lending the attacks an air of legitimacy.

Key points from the research:

• ClickFix activity is at its highest level to date.
• Fake AI installers and malicious search results are primary distribution vectors.
• Trusted chatbot platforms are being leveraged to deliver the malicious instructions.
• The approach evades traditional defenses by relying on user-executed commands.

There is no specific CVE or advisory identifier associated with this campaign in the source reporting, so none is cited here. Organizations should treat unsolicited instructions to paste commands into a terminal or Run dialog as a red flag, and user awareness training remains the most direct mitigation against this style of attack.

Source: BleepingComputer

Has your organization seen an uptick in ClickFix-style lures, and how are you training users to spot them?

North Korean threat actors are now incorporating a post-quantum cryptographic mechanism into their malware delivery chain, according to new research. The technique is being used to protect malicious payloads during distribution, marking a notable shift in how the group safeguards its infrastructure and evades detection.

The campaign blends both legacy and newly developed malware, with operators reusing established tooling alongside fresh components. This mixed approach allows the group to maintain tried-and-tested capabilities while introducing less familiar code that defenders may not yet recognize.

The delivery mechanism relies on post-quantum cryptography to secure the payload transfer, which researchers suggest is intended to future-proof the group's operations against improved interception and analysis capabilities. Details on the specific algorithms or implementation were not disclosed in the reporting.

• Payload delivery is secured using a post-quantum cryptographic mechanism
• Operations combine older and newer malware in the same campaign
• The activity is attributed to North Korean hackers tracked as part of the Lazarus group

This development is significant for defenders because it signals that state-sponsored actors are beginning to adopt next-generation cryptographic techniques in operational tooling, not just in theoretical research. Security teams should treat encrypted or unusually protected payload transfers as a potential red flag rather than assuming they are benign.

Source: BleepingComputer

How is your organization preparing for threat actors adopting post-quantum cryptography in their attack chains?

Hackers have compromised the infrastructure of Onamae Desktop Cloud, a widely used VPS provider in Japan, and deployed malware on as many as 26,739 customer servers, according to reporting from BleepingComputer.

The intrusion targeted the cloud platform's infrastructure rather than individual customer environments, which is why the impact scales across thousands of hosted servers. Details on the specific malware family, initial access vector, and timeline have not been fully disclosed in the available reporting, so administrators should treat any server hosted on the platform as potentially exposed.

At this stage, the key facts are:

• Affected service: Onamae Desktop Cloud (VPS hosting)
• Scale of impact: up to 26,739 customer servers with malware installed
• Attack vector: compromise of provider infrastructure

If your organization runs workloads on this provider, the practical priority is to treat hosted systems as untrusted until independently verified — rotate credentials and keys stored or used on those servers, review for unexpected processes, persistence mechanisms, and outbound connections, and rebuild from known-good images where compromise cannot be ruled out. Since the provider has not published detailed indicators of compromise in the reporting so far, detection efforts should lean on host-based hunting rather than relying on specific signatures.

Source: BleepingComputer

Do you or your organization host anything on Onamae Desktop Cloud, and if so, what steps are you taking to verify those servers are clean?

Google Chrome is rolling out new scam protections that use Gemini to detect deceptive websites and warn users about suspicious commands copied from ClickFix attacks.

The Gemini-powered detection is designed to identify scam sites and other deceptive pages and surface warnings to users before they interact with them. In parallel, Chrome is adding a safeguard for ClickFix-style attacks, where users are tricked into copying and running malicious commands themselves. When Chrome detects that a copied command looks suspicious, it will warn the user.

At this stage, the reporting does not specify affected Chrome versions, region-by-region availability, or detailed mitigation guidance beyond the built-in warnings. Users are advised to keep Chrome updated and to treat unexpected copy-and-run instructions on web pages with caution.

• Keep Google Chrome updated to receive the new protections
• Be wary of any website that instructs you to copy a command and paste it into a terminal or Run dialog
• Heed browser warnings about deceptive or suspicious sites and copied commands

Source: Unknown

Has your organization encountered ClickFix-style lures, and how are you handling them?

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued a warning that attackers are actively exploiting four vulnerabilities in Plex Media Server. The flaws are being chained together in attacks tracked as Plex2Shell, allowing adversaries to breach vulnerable servers.

CISA's alert confirms active exploitation in the wild, meaning unpatched Plex Media Server instances are at risk. Since the flaws are used in combination rather than in isolation, a single missing patch may not be enough to keep a server protected.

Administrators running Plex Media Server should take the following steps:

• Apply the latest security updates for Plex Media Server as soon as possible to address all four vulnerabilities
• Audit internet-facing Plex installations and restrict unnecessary exposure to the public internet
• Review server logs for signs of unexpected or suspicious activity

Given that the flaws are chained, patch coverage across all four issues matters — partial remediation leaves a path open.

Source: BleepingComputer

Has anyone confirmed whether their Plex deployment is fully patched against all four flaws, and how are you handling external exposure?

The PHP security team has pushed out emergency patches addressing two critical remote code execution flaws, tracked as CVE-2026-109618 and CVE-2026-109619 and collectively dubbed PHP2Shell. Because these vulnerabilities allow remote code execution, successful exploitation could let an attacker run arbitrary code on affected systems, making them a high-priority fix for anyone running PHP in production.

Details on the exact affected versions and exploitation conditions are limited in the initial advisory, so administrators should treat this as urgent and apply the available patches as soon as possible rather than waiting for further clarification. Given the severity classification, delaying updates leaves systems exposed to potential compromise.

Recommended actions:

• Apply the emergency patches released by the PHP security team immediately.
• Review your exposure to PHP-based services and prioritize internet-facing deployments.
• Monitor vendor channels for updated guidance on affected versions.

Source: Unknown

Has your organization already patched, or are you still assessing which systems are running affected PHP versions?

An intruder accessed a legacy system at OpenCode on the night of October 16, and the company has warned that third-party AI provider keys stored by users in OpenCode Console may have been exposed as a result.

Console is OpenCode's optional hosted service. Workspaces can save their own OpenAI, Anthropic, or Google API key there, and Console uses that key to call the provider on the workspace's behalf, allowing team members to use the models without handling credentials directly. Because those keys live in Console, any exposure of the underlying system puts the stored provider credentials at risk.

Key facts as disclosed:

• The intrusion involved a legacy system at OpenCode, reached on the night of October 16.
• Potentially affected data includes third-party AI provider keys saved in Console — specifically OpenAI, Anthropic, and Google keys.
• The company has not, in the disclosed information, confirmed which specific keys were actually accessed.

If your workspace stored provider keys in Console, treat them as potentially compromised until you hear otherwise. Rotating the affected keys with each provider is the safest course of action, and it is worth reviewing provider-side usage logs for any activity you don't recognize.

Source: The Hacker News

Did your team store provider keys in OpenCode Console, and have you rotated them yet?

A researcher has disclosed an unpatched vulnerability in Broadcom's Wi-Fi setup software that allows an attacker within radio range to execute code as root on affected routers. The disclosure comes from security researcher Quentin Kaiser, who published details on October 16.

The most concerning aspect of this flaw is that exploitation requires no network password and no pairing step. An attacker only needs to be within Wi-Fi range of a vulnerable device to attempt the attack.

Kaiser demonstrated the attack working against home gateways provided by three Belgian internet providers. In one of those cases, he was able to read the Wi-Fi password directly off the device. The flaw remains unpatched, meaning Broadcom-based routers that rely on the affected setup software may still be exposed.

At the time of reporting, no specific CVE identifier, advisory number, or patch version was provided. Affected users should monitor vendor advisories from Broadcom and their router or ISP provider for updates, and consider restricting Wi-Fi setup or WPS-style functionality where possible until a fix is available.

Source: The Hacker News

Is your organization running Broadcom-based routers or ISP-supplied gateways that could be exposed to this flaw?

A critical flaw in Docker Hub, the registry used to publish and download container images, allowed one user to push, pull, or delete images while authenticated as another user. Docker fixed the flaw on September 30 and stated that it found no evidence of exploitation in the wild.

According to a security advisory published on October 12, the issue resided in the feature that converts a personal account into an organization. The vulnerability had reportedly existed for roughly two years before being addressed.

Key points:

• Docker Hub users could potentially act on images under another user's identity due to the flaw.
• The vulnerability was tied to the personal-to-organization account conversion feature.
• Docker patched the issue on September 30.
• A security advisory was published on October 12.
• Docker says it has no evidence that the flaw was exploited.

No specific CVE ID or advisory identifier was provided in the source article. Administrators and users who rely on Docker Hub for image distribution should review the advisory and ensure their workflows align with Docker's current guidance.

Source: The Hacker News

Has your organization reviewed its Docker Hub account and organization conversion settings since this advisory was published?

Anthropic is warning that small AI models may be only months away from gaining the ability to self-replicate across IoT devices, including everyday hardware such as smart ovens and off-brand Android TV boxes.

According to the frontier AI lab, these small models could enable autonomous, self-propagating worm botnets that would be "challenging to shut down" — largely because "there's no centralized point to shut off." In other words, once such a botnet spreads, there is no single control server or chokepoint that defenders can take offline to stop it.

Key points from the warning:

• The capability could arrive within months, not years, per Anthropic's assessment.
• Targeted devices include consumer IoT gear like smart ovens and off-brand Android TV boxes.
• The resulting botnets would be self-propagating and autonomous, making containment difficult.
• The absence of a centralized point of control is what makes shutdown so hard.

For defenders, this reinforces the importance of segmenting IoT devices from critical networks, keeping firmware updated, and monitoring for unusual outbound traffic from consumer-grade hardware.

Source: The Hacker News

Does your organization have IoT devices exposed on the same network as critical systems, and how are you segmenting them?

An OpenAI employee has been arrested following allegations that he planted a hidden recording device inside an executive conference room at the company's San Francisco offices, reportedly to covertly capture sensitive conversations.

Abdulrahman Alfozan, 35, a Saudi national, faces a charge of using or endeavoring to use an electronic, mechanical, or other device to intercept oral communications. He was taken into custody by authorities, according to reporting on the case.

Key details so far:

• The device was allegedly placed in a conference room used for executive meetings.
• The charge relates to interception of oral communications rather than computer intrusion.
• No further technical details about the device itself have been disclosed.

The incident highlights the insider threat dimension of corporate security, where physical surveillance risks can be just as damaging as network-based attacks. Organizations handling sensitive discussions may want to review their physical countermeasures, such as room sweeps and device detection procedures, alongside their usual cybersecurity controls.

Source: The Hacker News

Does your organization have any controls in place to detect unauthorized recording devices in sensitive meeting rooms?

Microsoft has released its largest Patch Tuesday update to date, addressing 1,413 vulnerabilities in a single rollout. Among the fixes is a Windows Shell flaw that Microsoft says is already being exploited in the wild.

The update breakdown by product is substantial:

• 1,102 flaws in Windows
• 134 in Office
• 61 in Developer Tools
• 36 in SharePoint Server
• 22 in SQL Server

By vulnerability type, more than 670 relate to privilege escalation, followed by over 300 remote code execution issues.

With a volume this large and at least one flaw under active exploitation, patching should be treated as a priority rather than a routine monthly task. Organizations should review their exposure to the affected products and expedite deployment where feasible, particularly for internet-facing systems and anything covered by the actively exploited Windows Shell bug.

Source: The Hacker News

Has your organization started rolling out this month's patches, and are you prioritizing any product group first?

During an authorized assessment, an AI pentesting agent independently identified a critical authentication bypass on a major insurer's production website. The flaw itself was straightforward: a single login request allowed the user to choose where the one-time passcode was delivered, effectively undermining the OTP verification step. Interestingly, the technical exploitation was the easy part — the real challenge lay in proving the issue on a live production system.

• The vulnerability was discovered autonomously by an AI agent during an authorized engagement.
• The login flow trusted user-supplied input for OTP delivery destination.
• Validation and proof on the live site proved harder than the attack itself.

If your organization relies on OTP-based authentication, it is worth reviewing how delivery destinations are selected and whether user input can influence that choice. Have you audited your login flows for similar trust issues?

Source: The Hacker News
Does your organization's authentication flow allow users to control where OTPs are sent?

Researchers at ThreatFabric have disclosed a new Android banking trojan dubbed Hirudo that takes a different approach from typical overlay or accessibility-based malware. Instead of injecting fake screens on top of legitimate apps, Hirudo replaces genuine banking applications with purpose-built patched versions that disable the apps' own built-in security checks from the inside.

The Dutch mobile security firm found that the trojan targets the financial sector in Indonesia, with replacements identified for eight Indonesian banking applications. By running a modified version of the actual banking app, Hirudo can bypass protections that would normally detect tampering or hostile environments, making the fraud harder for both users and the banks' own defenses to spot.

This technique represents a notable escalation in financial fraud on Android, since the malicious app inherits the trust and functionality of the real one while the security mechanisms are stripped away.

Key points:

• Hirudo is an Android banking trojan analyzed by ThreatFabric.
• It swaps legitimate banking apps for patched versions that bypass the apps' internal security checks.
• Replacements were found for eight Indonesian banking applications.
• The approach differs from overlay-based trojans by operating from within a modified legitimate app.

Source: The Hacker News

Does your organization have controls in place to detect repackaged or tampered banking apps on user devices?

A team at security firm XBOW has demonstrated a full-chain Google Chrome exploit built with the help of a publicly available OpenAI model, chaining three previously unknown Chrome bugs into a single attack that executes code on a Windows machine when the victim simply loads a web page.

The researchers assembled the exploit in six days by directing AI agents running OpenAI's public GPT-5.6 Sol model. According to the company, the resulting chain was valued at $250,000.

Google has since confirmed all three vulnerabilities, fixed them, and paid XBOW its top bounty for the report.

Key points:

• Three then-unknown Chrome bugs were chained into one full exploit
• The attack achieves code execution on Windows from mere page load, with no additional user interaction described
• The exploit was developed in six days using AI agents driven by GPT-5.6 Sol
• Google confirmed and patched all three issues and paid the top bounty

The disclosure highlights how quickly AI-assisted tooling can be applied to vulnerability research, and why keeping Chrome updated matters even when individual bug details are not public.

Source: The Hacker News
Has your organization adjusted patch timelines for browsers in light of AI-accelerated exploit development?

Attackers are actively exploiting an OS command injection flaw in SiteGuard Server Edition, a web application firewall, to execute commands with root or SYSTEM privileges on affected servers. Successful exploitation gives an attacker the highest level of access on the host, making this a serious risk for any organization running the product.

The vulnerability stems from improper handling of input that allows injected operating system commands to run on the underlying server. Because the flaw can be triggered remotely, exposed SiteGuard instances should be treated as potentially compromised until patched and reviewed.

Key points:

• Affected product: SiteGuard Server Edition
• Impact: arbitrary command execution as root (Linux) or SYSTEM (Windows)
• Attack status: exploitation has been observed in the wild

Recommended actions for administrators:

• Apply the vendor's latest security update as soon as possible
• Restrict management interface access to trusted networks only
• Review server logs for suspicious command execution or unexpected processes
• Consider isolating or rebuilding any instance showing signs of compromise

If you run SiteGuard in your environment, prioritize patching and check for signs of unauthorized access before assuming the system is clean.

Source: Unknown

Is your organization running SiteGuard Server Edition, and have you already applied the vendor's fix?

The curl project has patched a memory corruption issue affecting how the tool handles HTTP/2 uploads. The flaw allows a malicious server receiving an upload to corrupt the uploading client's memory, and the researcher who reported it was able to turn that corruption into code execution on the client machine.

The fix landed on October 14 in curl 8.23.0.

Exploiting this in the wild is not straightforward. Taking over a client requires exact knowledge of its specific build and memory layout, which significantly narrows the pool of practical targets. According to the curl project, a real-world attack is expected to result in a crash rather than reliable compromise.

• Update to curl 8.23.0 or later to address the flaw.
• Treat uploads to untrusted or attacker-controlled HTTP/2 servers as a potential risk until patched.

Note: The project has not published a specific advisory identifier for this issue in the available reporting.

Source: The Hacker News

Has your organization already rolled out curl 8.23.0, or are you still assessing exposure across your build pipelines?

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued an urgent call for organizations to update their Ivanti Connect Secure (ICS) appliances and deployments to the latest version. The advisory follows the disclosure of a vulnerability that is being actively exploited in the wild.

The flaw, tracked as CVE-2026-104935, carries a CVSS score of 8.6 and is an authentication bypass affecting ICS. Given the active exploitation, CISA is recommending immediate patching rather than waiting for a scheduled maintenance window.

Adding to the urgency, honeypots have logged 105 exploit attempts targeting the vulnerability, indicating that attackers are already scanning for and attempting to leverage exposed appliances.

Key points for defenders:

• Update Ivanti Connect Secure appliances and deployments to the latest version as soon as possible.
• Treat internet-facing ICS appliances as high-priority assets given the active exploitation and honeypot activity.
• Review your exposure and confirm patch status across all ICS instances.

Source: The Hacker News

Has your organization already patched its Ivanti Connect Secure appliances, or are you still working through the update?

ConnectWise has disabled seven application identities as it investigates an incident where unknown threat actors gained unauthorized access to those identities and compromised Microsoft 365 tenants. The company disclosed the update on Saturday, confirming the investigation is ongoing.

The disabled application identities include:

• ConnectWise Cloud Backup — 506e08f9-6e9a-4da4-942b-a099a03644ae
• Additional ConnectWise application identities, based on the list published by the company

The company has not publicly detailed how the identities were obtained or the full scope of the affected tenants. The suspension of Cloud Backup appears to be a containment measure while the investigation proceeds.

Organizations using ConnectWise products — particularly those integrated with Microsoft 365 — should review their tenant configurations and monitor for any unauthorized application access or activity tied to the listed identity.

Source: The Hacker News

Are any members running ConnectWise Cloud Backup in their environments, and have you taken steps to audit your M365 application identities since this disclosure?