• The Beast ransomware group has emerged as a significant threat in the cybersecurity landscape, evolving from the Monster ransomware strain to establish itself as a formidable Ransomware-as-a-Service operation.

    Officially launched in February 2025, the group rapidly expanded their infrastructure by deploying a Tor-based data leak site in July, solidifying their presence in the underground ransomware ecosystem.

    By August 2025, Beast had publicly disclosed 16 victim organizations spanning the United States, Europe, Asia, and Latin America across diverse sectors including manufacturing, construction, healthcare, business services, and education.

    The ransomware operates with a distributed partnership model where each victim receives separate negotiation communications from different threat actors, suggesting a sophisticated affiliate network managing individual cases.

    BEAST ransomware group’s DLS (Source – ASEC)

    This approach complicates attribution and makes tracking the full scope of their operations considerably more challenging for security researchers and law enforcement.

    ASEC analysts noted that Beast employs a particularly insidious distribution methodology centered on network propagation following initial compromise.

    Rather than relying solely on email-based vectors, the malware actively scans for accessible SMB ports within compromised systems, allowing it to traverse network infrastructure and establish footholds across organizational environments.

    This lateral movement capability significantly amplifies the ransomware’s impact beyond isolated systems.

    Phishing remains a critical entry point, with Beast operators crafting deceptive emails disguised as copyright infringement warnings or fraudulent job applications.

    Beast ransomware GUI window (Source – ASEC)

    These campaigns frequently distribute the Vidar Infostealer alongside the ransomware payload, facilitating credential harvesting prior to ransomware deployment.

    This multi-stage approach enables attackers to gather sensitive information while preparing comprehensive encryption operations.

    SMB-Based Network Propagation and Lateral Movement

    The primary infection mechanism revolves around SMB port scanning from already-compromised systems.

    Once Beast gains initial access through phishing or other vectors, the malware systematically identifies active SMB ports and attempts lateral movement to shared network folders.

    This propagation strategy allows the ransomware to spread horizontally across organizational networks without requiring additional user interaction or external command-and-control communications for spreading purposes.

    The technique proves particularly effective in enterprise environments where network shares remain inadequately segmented or monitored.

    By exploiting inherent network trust relationships and shared resources, Beast maximizes infection scope while maintaining relatively low detection profiles during its lateral movement phase, making prevention through network monitoring and access controls essential defensive measures.

    Follow us on Google NewsLinkedIn, and X to Get More Instant UpdatesSet CSN as a Preferred Source in Google.

    The post New Beast Ransomware Actively Scans for Active SMB Port from Breached System to Spread Across Network appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Cybersecurity researchers have discovered a set of 10 malicious npm packages that are designed to deliver an information stealer targeting Windows, Linux, and macOS systems. “The malware uses four layers of obfuscation to hide its payload, displays a fake CAPTCHA to appear legitimate, fingerprints victims by IP address, and downloads a 24MB PyInstaller-packaged information stealer that harvests

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A sophisticated ransomware operation known as Beast has emerged as a significant cybersecurity threat, employing aggressive network propagation tactics that leverage Server Message Block (SMB) port scanning to infiltrate and encrypt systems across enterprise environments. The threat group, which evolved from the Monster ransomware strain, has been actively targeting organizations worldwide since its official launch […]

    The post Beast Ransomware Targets Active SMB Connections to Infect Entire Networks appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Australia’s competition regulator has filed legal proceedings against Microsoft for allegedly misleading approximately 2.7 million Australian consumers regarding subscription options and pricing for Microsoft 365 plans.

    The Australian Competition and Consumer Commission claims that Microsoft deliberately concealed the availability of cheaper alternative plans when integrating its AI assistant Copilot into subscription offerings.

    The core of the ACCC’s complaint centers on what regulators describe as deceptive communication practices following Microsoft’s decision to bundle Copilot with Microsoft 365 subscriptions starting October 31, 2024.

    Microsoft Sued for Microsoft 365 Subscriptions

    According to the ACCC, Microsoft informed subscribers that they must either accept Copilot integration with significantly higher prices or cancel their subscriptions entirely.

    What Microsoft allegedly failed to mention was the existence of Microsoft 365 Personal and Family Classic plans, which allowed customers to retain their existing features without Copilot at the original lower price point. The Classic plans remained virtually invisible to subscribers.

    They were only revealed deep within the subscription cancellation process, accessible only after users navigated to their Microsoft account subscriptions section and selected the cancel option.

    This hidden placement meant most consumers never discovered the alternative existed. The price increases accompanying Copilot integration were substantial.

    Email sent to subscribers informing them of the Copilot integration and price increase
    Email sent to subscribers informing them of the Copilot integration and price increase.

    Microsoft 365 Personal subscriptions rose 45 percent annually from $109 to $159, while Family plans increased 29 percent from $139 to $179. These increases prompted consumer complaints that ultimately triggered the ACCC investigation.

    Microsoft’s communication strategy relied on three key pieces: two emails sent to auto-renewing subscribers and a blog post.

    These messages conveyed that consumers faced a binary choice between accepting the expensive Copilot-integrated plans or cancelling entirely. The ACCC alleges this information was deliberately false and misleading by omission.

    “Following a detailed investigation, we will allege in Court that Microsoft deliberately omitted reference to the Classic plans in its communications and concealed their existence until after subscribers initiated the cancellation process to increase the number of consumers on more expensive Copilot-integrated plans,” according to regulatory statements.

    The page late in the cancellation process revealing the Classic plan
    The page is late in the cancellation process, revealing the Classic plan

    The regulator contends that many consumers would have selected the Classic plan had they known it existed, resulting in economic harm through unwanted price increases on renewed subscriptions.

    The ACCC is seeking consumer redress for affected subscribers along with penalties, injunctions, and declarations against both Microsoft Pty Ltd and Microsoft Corporation.

    For corporations breaching Australian Consumer Law, penalties can reach the greater of $50 million, three times the benefits obtained, or 30 percent of adjusted turnover during the breach period.

    The court will ultimately determine applicable penalties based on its findings. The case explicitly addresses only consumer-focused Microsoft 365 Personal and Family plans, excluding business and enterprise subscriptions.

    Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.

    The post Microsoft Sued for Allegedly Misleading Millions to Subscribe for Microsoft 365 Subscriptions appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A critical vulnerability in Magento, the popular e-commerce platform, is now rebranded as Adobe Commerce. Dubbed SessionReaper and tracked as CVE-2025-54236, this improper input validation flaw allows attackers to hijack user sessions and, in some cases, execute malicious code remotely.

    The discovery highlights the ongoing risks to online retailers, with over 250 Magento stores reportedly compromised overnight as threat actors ramp up their efforts ahead of the holiday shopping season.

    The vulnerability came to light on September 9, 2025, when Adobe issued an emergency security bulletin with patches to address it.

    At the time, the flaw was rated critical due to its potential for unauthorized access. However, the situation escalated dramatically on October 22, when researchers at Sansec publicly released a proof-of-concept exploit.

    This triggered a surge in attack attempts, transforming a theoretical risk into a widespread threat. Magento’s dominance in the e-commerce space, powering thousands of online stores worldwide, makes it a prime target, especially given its track record of high-profile vulnerabilities that have lured cybercriminals in the past.

    The SessionReaper Vulnerability

    At its core, SessionReaper stems from inadequate validation of user inputs in Magento’s authentication mechanisms. Attackers can manipulate session data to impersonate legitimate users, gaining control over admin panels or customer accounts without credentials.

    More alarmingly, advanced exploitation techniques demonstrated in the public proof-of-concept enable unauthenticated remote code execution (RCE).

    This could let intruders upload malicious scripts directly to servers, potentially stealing sensitive data like payment information or installing backdoors for long-term access.

    The vulnerability affects multiple versions of Adobe Commerce and Magento Open Source, including those that have not yet received the latest patches.

    Its CVSS score of 9.8 underscores the severity: high impact on confidentiality, integrity, and availability, with no privileges required for initial access.

    E-commerce operators running unpatched systems face immediate risks, as attackers need only a crafted request to initiate the hijack.

    Mitigations

    Akamai’s security team detected the first waves of exploitation shortly after the proof-of-concept surfaced.

    In just 48 hours starting October 22, attackers launched over 300 probes against more than 130 unique hosts, originating from 11 distinct IP addresses.

    These included sophisticated payloads like web shells, malicious scripts that grant persistent server control, and basic reconnaissance tools such as phpinfo queries to map server environments or echo commands to test injection success.

    Fortunately, Akamai’s Adaptive Security Engine, part of its App & API Protector suite, has been blocking these attempts by default. Existing rules, such as those targeting PHP web shell uploads, have neutralized threats without customer intervention.

    The company’s Security Intelligence Group continues to monitor developments, refining protections as new tactics emerge.

    Experts emphasize that while web application firewalls like Akamai’s provide a crucial layer of defense, the most reliable safeguard remains applying Adobe’s patches promptly.

    With Magento’s vast user base, unpatched sites could become easy prey for ransomware or data theft campaigns. Organizations should scan their environments immediately, update to the latest versions, and enable robust input validation to thwart SessionReaper and similar flaws.

    Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.

    The post Magento Input Validation Vulnerability Exploited In Wild To Hijack Session And Execute Malicious Codes appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A critical security vulnerability in XWiki collaboration software is being actively exploited by threat actors to deploy cryptocurrency mining malware on vulnerable systems. The flaw, tracked as CVE-2025-24893, represents a serious threat to organizations running unpatched XWiki installations. Cybersecurity researchers at VulnCheck have captured concrete evidence of active exploitation through their canary network. CVE Details […]

    The post XWiki Remote Code Execution Flaw Actively Weaponized for Coinmining appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Threat actors are actively exploiting multiple security flaws impacting Dassault Systèmes DELMIA Apriso and XWiki, according to alerts issued by the U.S. Cybersecurity and Infrastructure Security Agency (CISA) and VulnCheck. The vulnerabilities are listed below – CVE-2025-6204 (CVSS score: 8.0) – A code injection vulnerability in Dassault Systèmes DELMIA Apriso that could allow an attacker to

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Microsoft has issued a critical security update for ASP.NET Core to address CVE-2025-55315, a high-severity flaw that enables HTTP request smuggling and could allow attackers to bypass key security controls.

    Disclosed on October 14, 2025, this vulnerability has a CVSS v3.1 score of 9.9, making it one of the most severe issues ever reported in the ASP.NET ecosystem.

    The flaw stems from inconsistent handling of HTTP requests in the Kestrel web server component, which could let authenticated attackers inject hidden requests to escalate privileges or access sensitive data.

    While HTTP request smuggling is a well-known attack vector, this specific implementation in ASP.NET Core amplifies risks for web applications relying on the framework for authentication and authorization.

    Attackers exploit discrepancies between how proxies and servers parse headers like Content-Length and Transfer-Encoding, smuggling malicious payloads that evade normal processing.

    For instance, a crafted POST request might embed a concealed GET to an admin endpoint, tricking the system into executing unauthorized actions without detection.

    Understanding HTTP Request Smuggling

    At its core, HTTP request smuggling leverages parsing inconsistencies across network components, such as front-end proxies and back-end servers.

    An attacker sends a request with ambiguous headers, like combining Content-Length and Transfer-Encoding, causing the proxy to interpret it one way while the server sees the smuggled content differently.

    This can result in the second request bypassing rate limits, CSRF protections, or even authentication checks, leading to severe outcomes in multi-tiered environments.

    In the CVE-2025-55315 case, the Kestrel server’s failure to validate request boundaries under certain conditions allows smuggled requests to reach application logic intact.

    This affects all supported ASP.NET Core versions, including 8.0, 9.0, and 10.0 previews, particularly in setups with reverse proxies like NGINX or Azure Front Door.

    Exploitation requires network access and often low privileges, but the scope can extend to confidential data exposure or server crashes in worst-case scenarios.

    The vulnerability’s high score underscores its potential for chained attacks, from session hijacking to server-side request forgery.

    Not all applications are equally exposed; risks heighten if custom request parsing, header-based decisions, or skipped validations are in play.

    For regulated sectors handling sensitive data, unpatched systems could face compliance violations alongside direct threats like privilege escalation.

    Attack VectorPotential ImpactDepends On
    Smuggled login requestElevation of privilegeApp logic trusting headers
    Smuggled internal API callSSRFApp routing and endpoints
    Smuggled CSRF bypassSession hijackingCSRF token validation
    Smuggled injection payloadCode executionInput sanitization gaps

    Mitigations

    Microsoft urges immediate patching via the latest .NET updates for affected versions, followed by application restarts.

    Developers should audit request-handling code, especially around auth and input validation, while ensuring proxies normalize traffic to block smuggling attempts.

    Monitoring logs for anomalous patterns and testing with tools like those simulating HRS can further harden defenses. By applying these measures, organizations can safeguard ASP.NET applications against this pervasive threat landscape.

    Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.

    The post Microsoft Details ASP.NET Vulnerability That Enables Attackers To Smuggle HTTP Requests appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • The cybersecurity landscape continues to face persistent threats from emerging ransomware groups, with Gunra representing a significant concern since its emergence in April 2025. This threat actor has launched systematic attacks across multiple industries and geographic regions, including documented incidents in Korea. What makes Gunra particularly noteworthy is its dual-platform capability—the group distributes separate malware […]

    The post Gunra Ransomware Targets Windows and Linux with Dual Encryption appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Docker Compose, a cornerstone tool for developers managing containerized application harbors a high-severity vulnerability that lets attackers overwrite files anywhere on a host system.

    Discovered in early October 2025 by Imperva, the issue stems from improper handling of remote artifacts in Docker’s OCI support, enabling path traversal attacks without even launching containers.

    Assigned CVE-2025-62725 with a CVSS score of 8.9, the flaw affects millions of workflows in CI/CD pipelines, local development, and cloud environments. Docker swiftly patched it in version 2.40.2, urging users to update immediately.

    The vulnerability emerged as researchers probed Docker Compose’s new feature for OCI-based artifacts, which allows teams to share portable Compose projects via registries.

    These artifacts use simple “include” directives in YAML files to pull in configurations, environment files, and extensions. Behind the scenes, Compose downloads layers from the registry and reconstructs them in a local cache directory, guided by annotations like com.docker.compose.file or com.docker.compose.envfile.

    These annotations dictate file destinations, but the code in oci.go blindly concatenated them with the cache path, skipping normalization or boundary checks.

    Attackers could craft malicious artifacts with annotations to escape the cache and target sensitive locations, such as SSH keys or system configs.

    The danger lies in its stealth: it triggers during “read-only” operations like “docker compose config” or “docker compose ps,” which resolve remote includes without user intent to write files.

    A proof-of-concept demonstrates injecting an SSH public key into ~/.ssh/authorized_keys, granting remote access—all from a tricked developer running a routine command on an untrusted YAML file.

    This bug’s subtlety amplifies its threat. Developers often share Compose files in public repos or CI systems, unaware that a tampered “include” could fetch a poisoned artifact.

    In enterprise settings, cloud dev environments or automated builds become prime targets, as the process leaks server IPs during fetches and writes files with the Compose binary’s permissions.

    No container startup is needed, blurring the lines between safe inspection and exploitation. Impacts span Docker Desktop, Linux binaries, and integrated tools, potentially leading to full system compromise if the host runs as root or has broad write access.

    Docker’s fix introduces a validatePathInBase function that normalizes paths and rejects traversals or absolute references. Reported on October 9, confirmed by October 21, and released on October 27, the patch closes the gap without disrupting OCI features.

    Security experts emphasize auditing shared Compose files and running tools with the least privilege. As container orchestration evolves, this incident underscores the perils of trusting remote metadata, reminding developers that convenience must never outpace validation.

    With updates applied, Docker Compose regains its trusted status, but vigilance remains key in an era of interconnected DevOps.

    Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.

    The post Docker Compose Vulnerability Allow Attacks To Overwrite Arbitrary Files appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶