Microsoft Intune on Medium

YouTube video by Cooper

JPCERT/CCは10月23日、国内組織で相次ぐ不正アクセスへの注意喚起を更新し、AIを使った侵入試験（ペネトレーションテスト）の基盤「Cairn」などを悪用した攻撃の試行を5つ目の類型に加えた。公開されたWebアプリケーションの脆弱性を探って悪用を試み、ソフト更新を配るWSUSサーバーも狙っていた。攻撃元とみられるIPアドレス9件を公表し、接続記録の点検を求めている。

A European bank was breached through a poorly secured, third-party gateway before an attacker tried to exploit its Windows Server Update Services (WSUS) infrastructure. The case shows how stolen login details and weak access controls can put a bank’s central software systems at risk without a complex attack chain. The bank’s security team uncovered unauthorized VPN access attempts stretching across several months after spotting unusual activity on its central IT system. Investigators traced the intrusion to an external gateway managed by a third party, where strict authentication had not been properly enforced. Researchers from Unit 42 identified the intrusion and its attempted code execution, but their report does not name any malware family. Published on October 13, 2026, the investigation describes an opportunistic attacker whose noisy actions exposed basic security gaps rather than a confirmed, advanced spying operation. Attackers Breach European Bank The attacker used compromised credentials to sign in to internal systems through the gateway. Unit 42 did not name the appliance vendor or explain how those credentials were first obtained. The confirmed entry point was weak authentication on the externally managed device, not a disclosed gateway software exploit. That distinction matters because valid accounts can give an intruder access without requiring a new vulnerability. Earlier reporting on brute-force attacks against VPNs describes separate incidents involving weak passwords and appliances lacking multifactor authentication, showing why remote access settings deserve close review. Those incidents are not linked to this bank. Once inside, the intruder repeatedly scanned hosts and networks across several protocols, interacting with thousands of systems. Instead of quietly following one narrow path, the attacker searched broadly for more opportunities to gain access. Unit 42 said the volume of scanning and use of common system identifiers showed little effort to stay hidden. Over several months, the attacker also ran repeated password-guessing campaigns against internal systems, with administrator accounts a key focus. These attempts sought additional access while the intruder explored the environment. Separate coverage of automated VPN login attacks illustrates how repeated credential testing can threaten remote access services, although the bank’s reported password guessing occurred internally. The activity extended beyond logins. Automated web requests scraped internal pages and attachments, while the attacker searched operational and network shares. This exposed documentation during the intrusion. However, the report does not give a stolen data volume, identify affected customers, or confirm that customer banking records were taken. WSUS Exploit Attempt Stopped The attacker later targeted a remote code execution vulnerability in WSUS on the bank’s central configuration management server. That server handled software distribution across the organization, making it an attractive place to seek higher privileges and lasting access. Control of such a central service could have widened the incident’s impact. Unit 42 did not disclose the vulnerability’s CVE identifier. Although separate reporting on active WSUS vulnerability exploitation covers CVE-2025-59287, that identifier cannot be assigned to this bank incident from the published evidence. Keeping those cases separate avoids turning a related technical risk into an unsupported finding. Cortex XDR detected the attempt to run unauthorized code and contained the threat before it escalated. Unit 42 reported that the attacker was stopped from establishing persistent access or spreading further through the network. This containment followed earlier scanning, authentication attempts, and access to internal documentation; it did not prevent the initial breach. Responders reviewed endpoint records across thousands of systems and logs from dozens of Windows and Linux servers. They found no additional attacker presence or persistent backdoors. Bank leaders reviewed the exposed documentation and rotated all compromised credentials. The bank also expanded its Cortex XDR and Cortex XSIAM coverage and incident response support. The investigation highlights authentication, timely patching, and endpoint detection as core safeguards. Third-party management did not remove the bank’s exposure to a weak gateway configuration, while containment and follow-up hunting helped limit the damage. For security teams, the lesson is to review vendor-managed access with the same care as internal systems. The report calls for strict identity controls, timely updates, and endpoint monitoring. Checking these controls together is important because a valid login can otherwise turn an outside gateway into internal access. Indicators of compromise (IoCs):- Indicator category Source disclosure SHA-256, SHA-1, MD5 hashes Not published Attacker IP addresses Not published Domains and malicious URLs Not published Malware filenames and families Not identified Exploited WSUS CVE Not disclosed Note:   IP addresses and domains are intentionally defanged (e.g.,  [.] ) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM . Update defenses against new malware as soon as it appears. Integrate TI Feeds with data from 16K SOCs . The post Attackers Breach European Bank Through Third-Party Gateway and Target WSUS Server appeared first on Cyber Security News .

A threat actor used compromised credentials and a poorly configured third-party gateway to access a European bank, scan its network, and target internal…

Les certificats de Windows Update expirent en mai et juin 2027. Les PC pas suffisamment à jour perdront l'accès aux mises à jour. Qui est concerné ?

Fix Windows update error 0x80244010 on WSUS and Windows 10/11. Learn how to resolve catalog bloat, fix the test detectoid bug, and reset your update cache

Kurze Frage in die Runde der Blog-Leser und -Leserinnen, die einen Windows Update Server Service (WUS) verwenden. Heute morgen hat mich ein Leser per E-Mail kontaktiert, weil auf seinem WSUS ein…