Search/bsd
Known CVEs
0
Highest CVSS
—
In KEV
0
Vendor
nvi
Connections
9 relationships
VerdantBamboo Deploys BSD Variant of BRICKSTORM on Linux Appliances
A China-nexus cyber espionage group has been observed deploying a BSD variant of a known backdoor called BRICKSTORM, as well as two other malware families codenamed PLENET (aka GRIMBOLT) and AGENTPSD to target Linux systems. The activity has been attributed by Volexity to a threat cluster it tracks as VerdantBamboo, which it said overlaps with hacking groups known as Clay Typhoon (Microsoft), UNC5221 (Google), and Warp Panda (CrowdStrike). The cybersecurity company said it discovered the intrusion during an incident response engagement in September 2025, when it emerged that the adversary had compromised an unnamed victim's Egnyte Storage Sync system by exploiting a local privilege escalation flaw to deploy BRICKSTORM. The issue was addressed in Storage Sync version 13.13, released in March 2026. "The appliance had periodically been accessed by VerdantBamboo via IP addresses assigned through the victim organization's web SSL VPN," researchers Damien Cash, Paul Rascagneres, Steven Adair, and Tom Lancaster said in a technical report published last week. "The threat actor used the malware's proxying capabilities deployed on the Storage Sync system, along with compromised credentials, to access the victim's Microsoft 365 (M365) environment." It's assessed that these steps were undertaken to blend in with legitimate network traffic and evade Conditional Access policies, with the initial compromise occurring at least 18 months before. Following the initial remediation, VerdantBamboo is said to have staged a return, breaching the same organization by using stolen administrative credentials to connect to the firewall, and then abusing that access to configure web SSL VPN access to the device, connect to other systems, and deploy additional malware to a Synology Network Attached Storage (NAS) appliance. Further investigation has since uncovered that the threat actor had in fact compromised the victim organization's Managed Services Provider (MSP), specifically infecting its MSP's pfSense firewall with a BSD variant of BRICKSTORM around the same time the victim's Storage Sync system was also breached. It's believed that the victim was compromised through the threat actor's breach of the MSP. The two malware families deployed to the NAS appliance over SSH are as follows - PLENET (aka GRIMBOLT), a cross-platform backdoor developed in .NET Core and a new version of BRICKSTORM compiled using native ahead-of-time (AOT) compilation. It supports interactive shell, remote command execution, file manipulation, and command-and-control (C2) server switching. AGENTPSD, a Python-based reverse shell that likely functions as a fallback in case the primary implant ceases to function It's worth noting that the use of PLENET in the wild was reported by Google earlier this February in connection with attacks mounted by a suspected China-nexus threat cluster dubbed UNC6201 that exploited a vulnerability in Dell RecoverPoint for Virtual Machines (CVE-2026-22769, CVSS score: 10.0) as a zero-day since mid-2024. "VerdantBamboo is a highly sophisticated threat actor that seeks to leverage a combination of living-off-the-land techniques and malware deployment on systems that traditionally do not or cannot run EDR software," Volexity said. "This threat actor appears to have good knowledge of proprietary appliances, allowing them to deploy malware with customized persistence mechanisms. They also appear to have operational security discipline aimed at leveraging a limited number of domains and IP addresses per victim and setting up customized implant naming and persistence on a per-device basis."
thehackernews.comJun 8, 2026extracted
Tails 7.6 ships automatic Tor bridge retrieval and a new password manager
Tails 7.6 ships automatic Tor bridge retrieval and a new password manager Tails 7.6 is out, and for users operating on networks that block Tor, the most consequential addition is built-in bridge retrieval. The Tor Connection assistant can now detect when a direct connection to Tor is restricted and automatically request bridges suited to the user’s region. The request goes through the Tor Project’s Moat API, and the connection to that API is disguised via domain fronting, making it appear as traffic to an ordinary website. Previously, users on censored networks had to obtain bridges manually and enter them by hand. The feature closes a long-standing gap in Tails’ censorship-circumvention capability. Users who prefer to take action themselves can also select the option to request region-specific bridges directly from the connection assistant screen. Password manager switches from KeePassXC to Secrets Tails 7.6 replaces KeePassXC with the GNOME Secrets password manager as the default credential storage tool. Secrets has a simpler interface and integrates more tightly with the GNOME desktop environment. Accessibility features that were broken under KeePassXC, including the on-screen keyboard and cursor size adjustments, work again with Secrets. Existing KeePassXC database files are compatible with Secrets’ format, so stored credentials carry over without any conversion step. Users who depend on features specific to KeePassXC can still install it manually. Component upgrades and Qt5 removal The kernel moves to Linux 6.12.74. Tor Browser advances to 15.0.8, built on Firefox ESR 140.9. Thunderbird reaches 140.8.0esr. Electrum moves to 4.7.0, and that upgrade is tied directly to the removal of Qt5 from the distribution. The changelog confirms that Qt5 support packages have been stripped out entirely, and tests now verify that no Qt5 package ships with the build. The base distribution advances to Debian 13.4 (Trixie). Firmware packages also receive an update: firmware-nonfree moves to version 20260110-1, improving hardware support for graphics cards and wireless adapters on newer machines. The forge.js library, used in Tails’ web-facing components, upgrades to v1.3.3. The update includes a step to make it harder for external CDNs to target the project, and it brings the project’s license documentation into compliance with BSD 3-clause terms. Bug fixes targeting localization and upgrade reliability Three user-facing bugs are resolved in this release. Automated upgrades failed for users running Tails with the language set to Turkish; that problem is fixed. A broken link in the Thunderbird migration notification, the “Learn More” button that was supposed to point users to documentation, is restored. The confirmation dialog displayed when saving a language and keyboard layout to the USB stick in unencrypted form was not honoring available translations; it now renders in the user’s selected language. Upgrading Automatic upgrades are available for any installation running Tails 7.0 or later. The upgrade preserves data stored in Persistent Storage. Users whose automatic upgrade fails, or whose system does not start after an update, can follow the manual upgrade path available on the Tails documentation site.
helpnetsecurity.comMar 26, 2026extracted
Wine 11 brings major architectural work, synchronization changes, 600+ bug fixes
Wine 11 brings major architectural work, synchronization changes, 600+ bug fixes Wine, originally short for “Wine Is Not an Emulator,” is a compatibility layer that allows Windows applications to run natively on POSIX-compliant operating systems, including Linux, macOS, and BSD. Rather than running a full copy of Windows or simulating its internals, Wine works by translating Windows API calls into POSIX calls as applications run. The result is better performance, lower resource usage, and Windows applications that feel like a natural part of your desktop instead of something running in a separate environment. Wine 11 stable release Wine 11 marks a new stable release for the long-running compatibility layer that allows Windows applications to run on Unix-like operating systems. The release gathers a year of development into a single version and highlights progress in core system behavior, especially around synchronization and 32-bit application support on 64-bit systems. This release continues Wine’s steady pattern of shipping deep internal changes alongside incremental compatibility work. The focus in Wine 11 sits squarely on plumbing that affects many applications at once. Synchronization work takes a central role One of the main additions in Wine 11 is support for NTSYNC. Synchronization plays a foundational role in how Windows software manages threads, waits, and shared resources. Changes in this area influence responsiveness, timing behavior, and overall application stability. By bringing NTSYNC support into a stable release, the Wine project signals that this work has reached a level suitable for broad use. Applications that rely heavily on Windows synchronization primitives stand to benefit from more predictable coordination between threads and processes when running under Wine. This kind of change tends to affect a wide range of workloads, from desktop productivity tools to games and development software. The release treats NTSYNC as a platform-level improvement rather than a narrow fix, which aligns with Wine’s goal of matching Windows behavior as closely as possible across many use cases. A milestone for the new WoW64 architecture Wine 11 also marks the completion of the new WoW64 architecture. WoW64 refers to the ability to run 32-bit Windows applications on 64-bit systems, a requirement that remains relevant due to the volume of legacy and specialized software that still ships in 32-bit form. Calling out the completion of this architecture indicates that a restructuring effort has reached its intended state. This work affects how Wine builds, loads, and manages 32-bit and 64-bit components within the same environment. For users and administrators, the impact may surface through smoother execution of mixed workloads and fewer edge cases tied to application bitness. This milestone also matters for distributions and vendors that package Wine. A completed architecture provides a more stable foundation for long-term support releases and downstream maintenance. A stable release shaped by internal changes Wine’s stable releases often emphasize internal correctness and long-term maintainability, and this latest version follows that pattern. The headline items point to infrastructure that sits underneath many compatibility fixes, even when those fixes are not individually highlighted. Alongside synchronization and WoW64 work, Wine 11 includes a large set of smaller updates across graphics, input, media handling, system APIs, and developer tooling. These changes accumulate quietly across development cycles and then arrive together in a stable version. This approach means that some improvements only become obvious over time, as applications encounter fewer corner cases or require less configuration to run. Stable releases like Wine 11 aim to provide a dependable baseline that distributions and users can adopt with confidence for extended periods. Availability and adoption Wine 11 is available as a stable source release, with binary packages expected to flow through Linux distributions and third-party repositories on their usual schedules. Adoption timelines vary by platform and vendor, especially for environments that prioritize long testing cycles. For users who rely on Wine as part of daily workflows, Wine 11 represents a consolidation of recent development with particular attention to synchronization behavior and cross-architecture support. For developers and maintainers, the release offers a refreshed foundation for ongoing compatibility work across the Windows application ecosystem.
helpnetsecurity.comJan 13, 2026extracted
#BHUSA: Microsoft and Google Among Most Affected as Zero Day Exploits Jump 46%
Zero day exploitation surged by 46% year-over-year in the first six months of 2025, according to the Forescout Research – Vedere Labs H1 2025 Threat Review. Products from 27 vendors were found to be impacted by zero days, with Microsoft making up around a third (30%). Google products experienced the second highest volume of zero day exploits, at 11%, followed by Apple (8%), Ivanti (6%), Qualcomm (5%) and VMware (5%). A total of 23,583 vulnerabilities were published in the first half of 2025, averaging 130 new CVEs per day or 3930 per month. This represents a 15% increase compared to the same period in 2024. Additionally, 132 CVEs were added to the Cybersecurity and Infrastructure Security Agency (CISA)’s Known Exploited Vulnerabilities (KEV) catalog in H1 2025, an 80% year-over-year rise. Of these, 47% were originally published before 2025, many of which targeted perimeter infrastructure. Six impacted end of life products, meaning no patches are available for this equipment. Ransomware Actors Target Non-Traditional Equipment The Forescout report, published on August 4 during Black Hat USA, found that ransomware actors increasingly targeted non-traditional equipment, such as edge devices, IP cameras and Berkeley Software Distribution (BSD) servers. This approach is designed to bypass defenses, as such devices often lack endpoint detection and response (EDR). These devices are then used as footholds to enable lateral movement across IT, OT and IoT environments. One example of this tactic highlighted by the researchers was the deployment of Akira ransomware to Windows endpoints via a compromised IP camera in March 2025. Another was the VanHelsing group introducing a multi-platform encryptor that includes support for BSD UNIX. “We expect both asset types – IP cameras and BSD systems – to be increasingly targeted in the near future,” the researchers noted. “BSD, while niche, is gaining attention from ransomware operators.” The study also found that ransomware attacks grew 36% year-over-year, with 3649 documented attacks in H1 2025. Ransomware victims were recorded in 112 countries over the six-month period, a 9% increase from the 103 countries impacted in H1 2024. Nation State and Hacktivist Gangs Prevalent Forescout observed 137 threat actors undertake notable activity in H1 2025. Of these, 51% were attributed as financially motivated cybercriminals, 40% state-sponsored actors and 9% hacktivists. China was the country of origin for the highest proportion of these threat actors, at 33. This was followed by Russia (22 groups), Iran (eight), Turkey (four) and Brazil (three). The country of origin was unknown for 45 of the active tracked groups. The researchers also highlighted the blurred lines between hacktivists and nation-state groups, with Iran-aligned hacktivist groups heavily targeting critical OT environments. Daniel dos Santos, head of research at Forescout, commented: “What we’re seeing from Iranian-aligned groups is a shift toward more aggressive, state-influenced disruption tactics masked as activism. As geopolitical tensions escalate, these actors are becoming faster, louder and harder to attribute, and that makes their threat even more urgent for defenders to address.”
infosecurity-magazine.comAug 4, 2025extracted
Ransomware Group Uses AI Chatbot to Intensify Pressure on Victims
A threat actor claiming to have launched a new ransomware-as-a-service (RaaS) venture is leveraging AI chatbots in its negotiation panel to automate communication and apply psychological pressure on victims. In June 2025, a ransomware actor known by the alias $$$ publicly introduced a new RaaS brand, GLOBAL GROUP, on the Russian Anonymous Market Place (RAMP or Ramp4u) cybercrime forum. Researchers at Picus Security promptly conducted a forensic investigation across malware samples, infrastructure configuration and control logic, which included analyzing leaked API metadata, reverse-engineered binary code and threat actor behavior. They concluded that GLOBAL GROUP had very few new features but instead included capabilities found in the Mamona RIP and Black Lock ransomware families. In a July 21 report, Picus Security assessed that GLOBAL GROUP was a rebranding of these two groups. “At every layer, payload, delivery, control, and operation, GLOBAL reveals continuity and maturity more than innovation,” the researchers wrote. Negotiation Panel Equipped with an AI Chatbot However, one innovation the GLOBAL group has introduced is the use of an AI chatbot to kick off the negotiation process. The ransomware group offers a dual-portal model, directing victims to a Tor-based data leak site and a separate negotiation panel – a structure reminiscent of LockBit’s compartmentalized backend, suggesting that GLOBAL employs a double-extortion approach. Once on the negotiation panel, the victim is greeted by an AI-powered chatbot designed to automate communication and apply psychological pressure. The panel is designed for non-technical users, featuring prompts to upload a sample encrypted file for free decryption verification. All correspondence takes place over a secure channel, with a timer displayed to reinforce the urgency. Chat transcripts reviewed by analysts show demands reaching seven-figure sums, such as BTC9.5 ($1m at the time the negotiation process occurred), with escalating threats of data publication. GLOBAL’s affiliates have access to this panel in order to monitor negotiations, set ransom windows and even interact with victims directly via a mobile-friendly interface. “The integration of AI chat automation reduces the affiliate workload and ensures negotiations proceed even in the absence of human operators, enabling GLOBAL to scale victim engagement across time zones, languages, and organizational profiles,” the Picus Security researchers wrote. GLOBAL’s Techniques, Tactics and Procedures The majority of GLOBAL’s techniques, tactics, and procedures (TTPs) are borrow from Mamona RIP, Black Lock and Lockbit. The emerging ransomware group employs a cross-platform Golang-based payload, leveraging Go’s static linking and concurrency features to maximize encryption speed across Windows, Linux and macOS systems. This aligns with modern ransomware trends, where attackers favor Go for its efficiency in large-scale encryption. A key tactic is the reuse of a mutex string (Global\Fxo16jmdgujs437) previously seen in Mamona RIP, suggesting code inheritance rather than simple repackaging. This mutex ensures single-instance execution, preventing multiple ransomware processes from running simultaneously. Additionally, the group uses ChaCha20-Poly1305 encryption, a modern algorithm that provides both confidentiality and integrity, similar to Black Lock and LockBit, which also favor strong encryption schemes to deter recovery efforts. The ransom note is hardcoded into the binary and written to disk as README.txt, containing coercive language and a proof-of-decryption mechanism to build trust. This mirrors Mamona RIP’s approach, where psychological pressure is combined with technical validation. Notably, the group’s frontend API exposure reveals operational security failures, such as leaking backend SSH credentials and real IP addresses (e.g., 193.19.119[.]4), tying them to Russian VPS provider IpServer, the same infrastructure linked to Mamona. This suggests a shared development lineage or at least overlapping operational practices between the two groups. The GLOBAL ransomware builder is a RaaS platform with a customizable payload generator, allowing affiliates to configure encryption percentages, file extensions and additional malicious behaviors (e.g., process killing, log deletion, and self-deletion). This modular approach, where features are dynamically included at compile time, helps evade detection, a tactic also seen in LockBit’s builder. The ability to target ESXi, BSD and NAS appliances further expands its reach, similar to Black Lock’s focus on hybrid environments. The use of goroutines for concurrent encryption and filename encryption to hinder recovery efforts is an additional refinements that enhance its effectiveness, borrowing elements from both Mamona RIP and LockBit in terms of execution efficiency and evasion techniques. Detection, Mitigation and Response Strategies Against GLOBAL In their report, the Picus Security researchers shared a comprehensive list of strategies and measures security teams can implement to detect, mitigate and respond to the GLOBAL ransomware threat. These include: Detecting multithreaded ChaCha20-Poly1305 encryption by monitoring abnormal CPU/memory spikes and cryptographic API calls in Golang-based processes Identifying ransomware activity by tracking custom file extensions and encrypted filenames through file access monitoring and anomaly detection Monitoring for abuse of native utilities such as wevtutil, vssadmin, and net use, which attackers use for log tampering, shadow copy deletion and lateral movement Tracking unauthorized SSH access to cloud infrastructure, particularly from unusual geolocations or known malicious IPs linked to ransomware operations Detecting session hijacking and credential replay attacks by analyzing authentication anomalies in OWA (Outlook Web Access) and RDWeb (Remote Desktop Web Access) Conducting behavioral analysis to identify rare mutex strings (e.g. Global\Fxo16jmdgujs437), which may indicate single-instance ransomware execution Correlating lateral movement patterns originating from non-domain-joined endpoints, a common sign of initial access or privilege escalation Analyzing service-level telemetry for suspicious process chains (e.g., OpenProcess → TerminateProcess) and credential reuse across different protocols Simulating GLOBAL’s attack techniques using breach and attack simulation (BAS) to validate detection and response capabilities Assessing security controls to ensure they block real-world attack behaviors, not just static indicators of compromise (IOCs) Identifying and remediating blind spots caused by misconfigured detection rules or gaps in telemetry coverage Applying vendor-specific mitigations (e.g., Microsoft Defender, CrowdStrike, SentinelOne) to address validated security gaps Restricting the execution of Golang binaries in high-risk environments and monitoring for unusual Go-based processes Enforcing least-privilege access controls to limit ransomware’s ability to encrypt files or delete backups Disabling unnecessary native utilities (e.g., wevtutil, vssadmin) via Group Policy or application control policies Monitoring and blocking Tor-based command-and-control (C2) traffic and known ransomware leak site domains (e.g. .onion addresses) Implementing network segmentation to prevent lateral movement from compromised endpoints to critical assets
infosecurity-magazine.comJul 22, 2025extracted