• AccuKnox, a global leader in Zero Trust Cloud-Native Application Protection Platforms(CNAPP), today announced its partnership with Alice Blue India, a prominent brokerage andfinancial services firm, to strengthen its security and compliance frameworks across on-premand cloud workloads. The partnership was executed through channel partner Airowire. Leveraging AccuKnox’s security capabilities, Alice Blue aims to achieve enhancedvisibility, automated […]

    The post Alice Blue Partners With AccuKnox For Regulatory Compliance appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • AccuKnox, a global leader in Zero Trust Cloud-Native Application Protection Platforms(CNAPP), today announced its partnership with Alice Blue India, a prominent brokerage andfinancial services firm, to strengthen its security and compliance frameworks across on-premand cloud workloads.

    The partnership was executed through channel partner Airowire.

    Leveraging AccuKnox’s security capabilities, Alice Blue aims to achieve enhancedvisibility, automated compliance, and continuous protection within its infrastructure.

    The customer’s Chief Information Security Officer (CISO), Navneethan, expressed strongconfidence in the platform following a detailed proof-of-concept evaluation.

    Alice Blue’s Decision to Partner with AccuKnoxAfter evaluating multiple security vendors, Alice Blue selected AccuKnox for its technical depthand FinTech-grade compliance readiness.

    Key differentiators include:

    ● Agentless Zero Trust CNAPP architecture ensuring low operational overhead

    ● Rapid deployment with measurable visibility and compliance outcomes

    ● Alignment with India’s key regulatory frameworks RBI, SEBI, PCI-DSS, ISO, andSOC 2

    Customer Testimonials

    “At Alice Blue, securing our trading infrastructure and maintaining regulatory compliance are toppriorities,” said Navneethan, CISO, Alice Blue India, “Partnering with AccuKnox allows us toleverage world-class Zero Trust CNAPP capabilities while automating compliance across multi-cloud workloads.

    This collaboration strengthens both our internal security posture and theservices we deliver to our customers.

    ”“Financial institutions like Alice Blue require robust,scalable, and compliant security frameworks.

    AccuKnox Zero Trust CNAPP platform providesend-to-end protection from code to cognition, enabling Alice Blue to reduce risk, automatecompliance, and focus on domain innovation.

    This partnership highlights the impact of channelcollaboration in delivering secure, modern cloud environments.” said Rahul Jadhav, CTO atAccuKnox”We are thrilled to support Alice Blue India in deploying AccuKnox’s Zero TrustCNAPP platform, this partnership demonstrates how channel collaboration can acceleratesecurity adoption in regulated industries, delivering measurable outcomes in compliance,visibility, and threat protection.”said Hemath Raj, Account Manager, Airowire Networks.

    About Airowire

    Airowire Networks is a network and cybersecurity solutions provider specializing in infrastructuremodernization, cloud security, and managed detection services.

    With a strong regional presenceand a focus on delivering secure digital transformation.

    About Alice Blue

    Alice Blue is a leading brokerage and financial services company offering advanced tradingplatforms, real-time analytics, and customer-centric solutions.

    With a strong commitment toinnovation and regulatory compliance.

    About AccuKnox

    AccuKnox is a Zero Trust CNAPP platform that delivers runtime protection, agentless riskassessment, and comprehensive visibility across cloud, container, and AI workloads.

    A corecontributor to CNCF open-source projects KubeArmor and ModelArmor.

    Contact

    PMM

    Syed Hadi

    AccuKnox

    syed.hadi@accuknox.com

    The post Alice Blue Partners With AccuKnox For Regulatory Compliance appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • The U.S. Justice Department has announced a significant crackdown on North Korean cybercrime operations, securing five guilty pleas and initiating civil forfeiture actions totaling over $15 million against schemes orchestrated by the Democratic People’s Republic of Korea (DPRK). The elaborate fraud network impacted more than 136 American companies, generating $2.2 million for the North Korean […]

    The post North Korean Hackers Breach 136 U.S. Companies, Earning $2.2 Million appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Cybersecurity researchers have unveiled comprehensive detection methodologies for NotDoor, a sophisticated backdoor malware that leverages Microsoft Outlook macros for covert command and control operations. The malware, attributed to the Russian state-sponsored threat group APT28 (Fancy Bear), represents an evolution in email-based persistence techniques that can evade traditional security controls. NotDoor was first identified by Lab52, […]

    The post New Detection Methods Uncovered for Outlook NotDoor Backdoor Malware appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Cybersecurity researchers have observed a dramatic escalation in attacks exploiting a critical XWiki vulnerability, with multiple threat actors now leveraging CVE-2025-24893 to deploy botnets, cryptocurrency miners, and custom malware toolkits.​ The vulnerability, initially detected by VulnCheck’s Canary Intelligence system on October 28, 2025, has rapidly evolved from a single attacker’s exploit into a widespread multi-actor […]

    The post Hackers Weaponize XWiki Flaw to Build and Rent Out Botnet Networks appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A critical vulnerability allowing attackers to inject malicious code into Cursor’s embedded browser through compromised MCP (Model Context Protocol) servers.

    Unlike VS Code, Cursor lacks integrity verification on its proprietary features, making it a prime target for tampering.

    The attack begins when a user downloads and registers a malicious MCP server through Cursor’s configuration file. Once enabled, the rogue server injects arbitrary JavaScript directly into Cursor’s internal browser environment.

    Attackers exploit the absence of checksum verification to modify unverified code during server registration.

    How the Attack Works

    The injection mechanism uses a simple but effective technique: “document.body.innerHTML ” is replaced with attacker-controlled HTML, completely overwriting the page and bypassing UI-level security checks.

    This allows attackers to display convincing fake login pages or malicious content without raising suspicion.

    Knostic researchers demonstrated this vulnerability by creating a proof-of-concept that harvested user credentials through a fake login page and transmitted them to a remote server.

    The stolen credentials could grant attackers complete access to a developer’s workstation and corporate network. The attack requires minimal steps: users must enable the MCP server and restart Cursor.

    Once it runs, the malicious code stays active in every browser tab in the IDE, giving attackers ongoing access to the system.

    This vulnerability highlights a growing threat to the developer ecosystem. MCP servers require broad system permissions to function, meaning compromised servers can modify system components, escalate privileges, and execute unauthorized actions without user awareness.

    The threat extends beyond individual developers, according to the Knostic report. Organizations face significant supply chain risks as malicious MCP servers, IDE extensions, and prompts can execute code on developer machines, now the new security perimeter.

    Attackers can expand their reach from targeted developers to entire corporate networks. The vulnerability underscores how AI coding tools and agents introduce expanding attack surfaces daily.

    Unlike traditional development tools, these platforms integrate multiple external components with minimal visibility or control mechanisms.

    Organizations should implement strict policies around MCP server adoption, verify server sources, and monitor IDE configurations. Knostic developers should exercise caution when downloading extensions and servers from untrusted sources.

    The cursor was notified prior to publication, and the researchers withheld exploit code to prevent widespread abuse.

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

    The post Hackers Use Rogue MCP Server to Inject Malicious Code and Control the Cursor’s Built-in Browser appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • The Amphibious Ready Group and Marine Expeditionary Unit—the ARG/MEU—is the Nation’s most flexible and effective formation for projecting power from the sea. Three ships, carrying a 2,200-Marine combined arms team, maneuver as sovereign U.S. territory anywhere on the globe. They respond in hours, not weeks. They can put Marines ashore without relying on ports, airfields, or permission from another country. They bring command and control, aviation, fires, logistics, and a reinforced infantry battalion—all from the sea, ready to fight on arrival.

    Despite the MEU’s proven value in warfighting and deterrence—and its growing combat power under our Force Design initiative—our nation’s maritime expeditionary capability has steadily eroded. Today, we sit at 32 amphibious ships, barely meeting the congressionally mandated floor. With amphibious-ship readiness below 50 percent, we are well short of what’s needed to support three consistently forward-deployed ARG/MEUs. The Marine Corps has identified this gap for years, and leaders within the Department of the Navy are now moving with urgency to stabilize the fleet and drive investment in the industrial base for military shipbuilding.

    As Commandant, I am addressing this amphibious capability shortfall through two initiatives outlined in my Planning Guidance. First, we must restore our amphibious capacity through a return to a 3.0 ARG/MEU presence: three forward-postured MEUs, each with three amphibious warships, persistently positioned around the globe. This has long been the standard, and it remains the Marine Corps’ North Star. Our combatant commanders, the Joint Force, and our civilian leaders rely on these formations to campaign, deter, and respond without delay and without any permission needed from a third party for access, basing or overflight.

    Second, we are modernizing the MEU through Force Design, ensuring it evolves in stride with the changing character of war. Just as our Marine Littoral Regiments are receiving long-range fires, resilient command and control, unmanned systems, and advanced sensing networks, those same capabilities are being fielded across the MEUs, advancing their role as a flexible, multi-domain force from the sea.

    A needed force for a maritime nation

    For 250 years, Marines have been first to fight—closing with the enemy, defending our nation, always forward, always ready, and often from the sea. Our enduring warrior ethos reflects the fundamental truth that the nature of war does not change—but the character of war does—and so must the way we fight.

    After the Second World War, as a new era of global tension took shape, the nation needed a force that could respond rapidly and operate forward without waiting on ports, bases, or permission. That requirement came into sharp focus in the early years of the Cold War, when the Navy and Marine Corps were asked to counter nuclear-armed adversaries, dispersed flashpoints, and threats with no notice. The logic behind the MEU’s design was operational from the start: built to be ready now, to maneuver from the sea, to project power inland, and to shape the fight before it began.

    The advent of nuclear weapons reshaped our approach to amphibious operations. What worked at Okinawa or Inchon required rethinking in the face of a threat that punished mass and predictability. The Corps responded by developing new ways to come from the sea without confining the assault to a narrow beachhead. Vertical envelopment was added to the beach assault, expanding the maneuver space and giving commanders more options.

    To support this new approach, the Marine Corps restructured its forward-deployed forces. Rotary-wing lift, aviation-delivered fire support, and integrated logistics gave rise to the Marine Air-Ground Task Force concept: an integrated formation that could launch from sea, land inland, and fight immediately. By the late 1980s, the MAGTF formations called MEUs were operating routinely from the Mediterranean to the Western Pacific. They weren’t held in reserve. They were deployed forward.

    During the Cold War, the MEU’s value was recognized in operational war plans. One of the clearest examples was in the High North. If Soviet forces pushed into Norway, a MEU embarked aboard amphibious shipping would land in the fjords to reinforce Norwegian defenders and counter Soviet naval infantry along the flanks. That wasn’t a theory, it was backed up by prepositioned equipment, rehearsed in exercises like Teamwork and Northern Wedding, and respected by Soviet planners who were forced to hedge against it.

    The operational rationale that validated the MEU in the past remains just as relevant today. It creates problems adversaries cannot ignore at a cost the Nation can sustain—turning shorelines into entry points, projecting power inland, and transforming maritime access into combat power for the Joint Force. Forward-deployed at sea, the ARG/MEU deters by denying the adversary decision space, shaping the environment in our favor, and introducing risk before conflict begins. Its maneuverable posture gives it both survivability and combat credibility. And it remains able to operate independently, integrate with the fleet, or reinforce allies—preventing escalation and–if required—moving rapidly to combat.

    Toward a modern MEU

    As the character of warfare continues to evolve—driven by a connected world and rapid advances in technology, tomorrow’s fight will be more connected and lethal. Success will depend on speed, precision, and adaptability in a battlespace that is sensor-rich and contested across all domains.

    Force Design, launched in 2019, remains the Marine Corps’ framework for adapting to the changing character of war across our MEUs, Marine Expeditionary Brigades, Marine Expeditionary Forces, and Marine Littoral Regiments. It is guided by a campaign of learning that refines how we man, train, and equip the force to deter aggression and close gaps in a contested, multi-domain fight. That learning is what drives Force Design’s modernization initiatives. The technology fielding that began with the Marine Littoral Regiments is now advancing through the MEUs and across the Corps—shaped by experimentation, real-world operations, and the integration of long-range fires, resilient C2, and unmanned systems. These advances enable MEUs to operate as agile, sea-based maneuver elements—able to sense, shoot, and support the Joint Force from sea to shore.

    The MEU remains a forward-deployed, combined arms team: light enough to deploy quickly, but potent enough to punch above its weight. Its combat power is built around three core advantages: precision fires, adaptable command and control, and enhanced survivability. When armed with HIMARS, NMESIS, loitering munitions, and supported by fifth-generation F-35B sensor fusion, the MEU will deliver effects into areas other formations cannot reach. Its command element is already optimized to serve as an agile hub for multi-domain operations by integrating kinetic and non-kinetic effects, sensors, and decision-makers across the battlespace. Future dispersed C2 nodes, unmanned platforms, and advanced manufacturing capabilities will strengthen its ability to maneuver, sustain, and adapt under pressure.

    Getting to a 3.0 ARG/MEU

    Modernization isn’t enough. Advanced capabilities only matter if we can get them forward, on time, and where the fight is. The MEU is evolving to meet tomorrow’s demands, but realizing its full potential depends on having a fleet that can support it. That’s one of the biggest challenges we face today.

    The problem is capacity. In 1991, the fleet had more than 60 amphibious warships—enough to sustain global presence and reinforce war plans across multiple theaters. But as the nation focused on extended land campaigns in the Middle East, the amphibious fleet was deprioritized. By 1997, that number had dropped to 40, and by 2016 it stood at just 31. Today the amphibious fleet has 32 ships whose average readiness hovers around 45 percent. Shipyards are strained, timelines are slipping, and hulls are aging faster than we can replace them.

    Sustaining a 3.0 ARG/MEU presence will require 31 amphibious ships at 80 percent readiness. The recent LHA/LPD block buy was a step in the right direction, but we must continue to build on this momentum. The Marine Corps is working closely within the broader defense establishment to maintain the fleet, improve readiness, and set conditions for a stronger future. The effort will take broad cooperation, sustained investment, and shared urgency across the U.S. government, industry, and the Department of War.

    Conclusion

    The Corps’ North Star must remain a steady 3.0 ARG/MEU presence: three continuous, three-amphibious warship formations forward deployed—one from the East Coast, one from the West, and one patrolling from Okinawa, Japan. (If you ask our combatant commanders what they need, the answer isn’t a total of three ARG/MEUs; it’s closer to five or six.) 3.0 is the minimum required to provide our nation and the Joint Force with a capability that can serve as both a warfighting formation and a cross-service integrator. It’s what keeps pressure on our adversaries, supports the maritime fight, and gives combatant commanders and national decision makers scalable options they can employ without delay to buy time, create decision-space, and if required to do so, be first to fight.

    Right now, we’re falling short. Every day below that mark costs time, space, and initiative. The ARG/MEU is more than  just a crisis-response formation, it is how a maritime nation extends influence, demonstrates resolve, and turns naval capability into action. It reflects who we are as a service: forward, agile, and ready to fight. The world and our adversaries are moving fast, and so must we. In a battlespace defined by access, timing, capability, and tempo, the ARG/MEU stands out: a formation that reaches the fight without relying on basing or buildup and bringing with it a MAGTF that delivers immediate combat power and multi-domain effects.

    Its capabilities continue to evolve. Its demand by combatant commanders continues to grow. But one thing hasn’t changed: Marines. Their cohesion and resolve turn emerging technologies into battlefield advantage. When they come from the sea, they bring C2, fires, logistics, aviation, and a reinforced infantry battalion—ready to act forcibly before anyone else can.

    The MEU remains the connective tissue between sea and land, deterrence and decision, day-to-day campaigning and high-end warfighting. What began as a Cold War solution has since matured into forward-deployed expression of American resolve.

    For 250 years, Marines have fought forward—ready at a moment’s notice, often from the sea. That legacy endures in the ARG/MEU: first to the fight, lethal on arrival, and ready for anything. This unique capability remains a cornerstone of American strength that secures peace. It must be sustained.

    Gen. Eric Smith is the 39th Commandant of the United States Marine Corps.

    ]]>

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A new open-source tool called SilentButDeadly has emerged, designed to disrupt Endpoint Detection and Response (EDR) and antivirus (AV) software by severing their network communications.

    Developed by security researcher Ryan Framiñán, the tool leverages the Windows Filtering Platform (WFP) to create temporary, bidirectional blocks on EDR cloud connectivity, isolating threats without terminating processes.

    His approach builds on the 2023 EDRSilencer technique, offering improved operational safety through dynamic, self-cleaning filters.

    The tool addresses a key vulnerability in modern EDR architectures, which rely heavily on cloud-based telemetry for real-time analysis and updates. By preventing outbound data uploads and inbound command reception, SilentButDeadly effectively neuters remote management and threat intelligence sharing.

    Unlike aggressive evasion methods that disrupt security processes, it focuses on stealthy network isolation, making it ideal for red-team exercises and malware analysis in controlled environments. Framiñán’s implementation ensures no persistent artifacts remain unless explicitly configured, reducing forensic footprints.

    SilentButDeadly Execution

    SilentButDeadly’s execution unfolds in structured phases, beginning with privilege verification using Windows APIs like CheckTokenMembership() to confirm administrator access. Users are prompted interactively to proceed, enhancing control.

    The core discovery phase scans running processes via CreateToolhelp32Snapshot(), matching against a predefined list of EDR targets such as SentinelOne’s SentinelAgent.exe and Microsoft Defender’s MsMpEng.exe. Once identified, it queries full process paths and initializes WFP with a dynamic session flagged by FWPM_SESSION_FLAG_DYNAMIC for automatic cleanup.

    Network blocking is implemented at ALE layers: outbound via FWPM_LAYER_ALE_AUTH_CONNECT_V4 and inbound via FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4, using high-priority weights (0x7FFF) and process-specific AppID conditions.

    Filters convert executable paths to WFP blobs with FwpmGetAppIdFromFileName0(), ensuring precise targeting. Following isolation, the tool disrupts services by stopping them gracefully and setting startup types to SERVICE_DISABLED, preventing restarts. A summary displays affected processes, block counts, and WFP status before optional cleanup removes all rules.

    Supported targets include SentinelOne, Windows Defender, and Defender ATP (MsSense.exe), with extensibility via a simple array. Command-line options like –verbose for logging and –persistent for enduring filters add flexibility, while robust error handling provides graceful fallbacks.

    Security features emphasize legitimate APIs only, no kernel tweaks, though it requires admin rights. Operationally, it severs EDR updates, telemetry, and scans, but leaves local detection intact. Detection risks include WFP event logs (IDs 5441, 5157) and service modifications, detectable via netsh wfp commands or PowerShell queries.

    Framiñán stresses ethical use for authorized testing, urging defenders to monitor WFP changes and implement resilient EDR designs with local caching.

    Available on GitHub under loosehose/SilentButDeadly, the tool sparks discussions on EDR dependencies, potentially driving vendor improvements. As cyber threats evolve, such research underscores the need for balanced architectures less reliant on constant connectivity.

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

    The post SilentButDeadly – Network Communication Blocker Tool That Neutralizes EDR/AV appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • The botnet malware known as RondoDox has been observed targeting unpatched XWiki instances against a critical security flaw that could allow attackers to achieve arbitrary code execution. The vulnerability in question is CVE-2025-24893 (CVSS score: 9.8), an eval injection bug that could allow any guest user to perform arbitrary remote code execution through a request to the “/bin/get/Main/

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A serious security flaw in Cisco Catalyst Center Virtual Appliance has been discovered that allows attackers with low-level access to gain full administrator control over affected systems.

    The vulnerability, tracked as CVE-2025-20341, impacts virtual appliances running on VMware ESXi and carries a high severity rating with a CVSS score of 8.8.

    This flaw poses a major risk to organizations using these systems for network management and monitoring.

    The vulnerability stems from poor input validation within the system. When users submit data through web requests, the software fails to properly check and verify the information.

    This oversight creates an opportunity for attackers to send specially designed HTTP requests that trick the system into granting them higher privileges.

    The attack can be carried out remotely over the network, making it particularly dangerous for exposed systems.

    What makes this vulnerability concerning is that an attacker only needs basic access credentials to exploit it.

    Someone with Observer role permissions, which are typically given to users who need to view system information, can use this flaw to elevate their privileges to Administrator level.

    Once they gain administrator access, attackers can create new user accounts, modify system settings, and perform other unauthorized actions that compromise the security of the entire network infrastructure.

    Cisco security researchers identified this vulnerability during work on a support case with the Technical Assistance Center.

    The company has confirmed that no public exploits have been observed yet, which gives organizations a window to patch their systems before widespread attacks begin.

    Technical Details and Mitigation

    The vulnerability affects Cisco Catalyst Center Virtual Appliance versions 2.3.7.3-VA and later releases.

    The security flaw is rooted in insufficient validation mechanisms that process user-supplied input through HTTP requests.

    When the system receives these crafted requests, it fails to properly sanitize the data before processing privilege escalation operations.

    Cisco has released version 2.3.7.10-VA as the fixed release that addresses this security issue. Organizations running affected versions should upgrade immediately to this patched version.

    CVE IDCVSS ScoreAffected ProductVulnerable VersionsFixed VersionAttack Vector
    CVE-2025-203418.8 (High)Cisco Catalyst Center Virtual Appliance (VMware ESXi)2.3.7.3-VA and later2.3.7.10-VANetwork (Remote)

    The company has stated that no workarounds are available, making the software update the only effective way to protect against this vulnerability.

    Hardware appliances and AWS-based virtual appliances are not affected by this issue.

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

    The post Cisco Catalyst Center Vulnerability Let Attackers Escalate Priveleges appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶