<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
    <title>Triage Security Blog</title>
    <description>Latest news, insights, and updates from Triage Security.</description>
    <link>https://shortwaveslive.vdp.triagesecurity.ai/blog</link>
    <atom:link href="https://shortwaveslive.vdp.triagesecurity.ai/blog/rss.xml" rel="self" type="application/rss+xml" />
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 15:13:04 GMT</lastBuildDate>
    
    <item>
        <title>Evaluating the impact of geopolitical shifts on APT28 infrastructure campaigns and Windows zero-day utilization</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/6509684e-2d76-4ffd-a5d6-ed3ceeccfa98</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/6509684e-2d76-4ffd-a5d6-ed3ceeccfa98</guid>
        <pubDate>Fri, 10 Apr 2026 03:12:01 GMT</pubDate>
        <description>Recent geopolitical developments and the public disclosure of a Windows local privilege escalation vulnerability are currently shifting priorities for security operations centers. This analysis details the technical mechanisms behind APT28’s Prismex suite and the BlueHammer zero-day, providing security teams with actionable recommendations for infrastructure hardening and detection.</description>
        <content:encoded><![CDATA[
            In the last 24 hours, the intersection of geopolitical shifts and technical vulnerabilities has redefined the immediate priorities for security operations centers. While international headlines focus on a fragile ceasefire between the United States and Iran, the digital environment remains highly active. Historical data and fresh intelligence indicate that military truces rarely equate to a pause in digital operations; instead, they often serve as transition periods where unauthorized parties shift from regional affected organizations to broader asymmetric campaigns. As the security community evaluates the public release of a Windows zero-day vulnerability alongside the escalation of APT28’s global infrastructure operations, the operational guidance for defenders is clear: diplomatic pauses often provide windows for malicious actors to refine their methodologies and adjust their focus.

## Infrastructure operations and the Prismex suite

The sustained activity from the Russian military intelligence-linked group APT28, also known as Fancy Bear or Forest Blizzard, has reached a higher operational tempo this week. Recent analysis identifies an ongoing effort to gain unauthorized access to government and critical infrastructure environments through a sophisticated software suite dubbed Prismex. This campaign, which has been escalating since January 2026, focuses on defense supply chains across Ukraine and its European allies.

The activity requires careful monitoring due to the group's ability to blend advanced methods, such as steganography and COM hijacking, with specific vulnerabilities in Microsoft’s infrastructure. Specifically, APT28 has been observed leveraging CVE-2026-21513, an unpatched vulnerability in the MSHTML framework, and CVE-2026-21509, an OLE-related bug in Microsoft Office. These are used to establish initial access and route command-and-control traffic through legitimate cloud services.

Beyond software vulnerabilities, APT28 is actively focusing on the hardware that underpins remote work and small-office environments. By leveraging CVE-2023-50224 in TP-Link, MikroTik, and EdgeOS routers, the group alters DNS and DHCP configurations. This routing modification enables adversary-in-the-middle operations against encrypted communications. If a user bypasses a certificate warning, the unauthorized party can collect OAuth tokens and credentials. This infrastructure-level activity is frequently paired with NTLMv2 hash relay operations. By sending unsafe calendar invites that trigger the now-patched CVE-2023-23397, the group forces connections to external SMB servers. This captures authentication hashes, allowing them to move laterally within a network without requiring a user’s password.

## The BlueHammer privilege escalation flaw

Simultaneously, the security community is evaluating the public release of "BlueHammer," a local privilege escalation (LPE) zero-day affecting Windows environments. Published by a researcher frustrated with Microsoft’s disclosure timeline, the proof-of-concept (PoC) code triggers a time-of-check to time-of-use (TOCTOU) race condition within the Windows Defender signature update mechanism.

By forcing a write to a restricted path through path confusion, a local user can gain access to the Security Account Manager (SAM) database. This access permits the extraction of password hashes and a subsequent escalation to administrator rights via pass-the-hash techniques. While the method is currently most reliable on Windows desktop versions and requires an existing local foothold, the publication of a documented reimplementation, SNEK_BlueWarHammer—reduces the friction for malicious actors to incorporate this technique into post-access methodologies.

## Geopolitical shifts mask digital reconnaissance

These technical developments occur alongside complex geopolitical realignments. Despite the announcement of a temporary truce in the Middle East, high-profile Iranian operations like Handala have publicly stated that while they may pause certain activities affecting the U.S., their focus will shift to other regional organizations. Security analysts observe that these operational pauses often mask underlying preparation.

During previous ceasefires, such as the late 2023 truce in Gaza or the Black Sea agreements in Ukraine, unauthorized digital activity often increased as an asymmetric pressure valve. Malicious actors use these windows to conduct reconnaissance or launch phishing campaigns against secondary organizations and allies, maintaining strategic pressure without violating kinetic military agreements. This pattern is visible today, with groups like the 313 Team and Conquerors Electronic Army continuing DDoS and authentication portal operations against Australian and U.S.-based environments despite the broader diplomatic cooling.

## Foundational hardening and mitigation

For security teams, these combined technical methods necessitate a shift toward rigorous internal monitoring and foundational hardening. Since BlueHammer and APT28’s relay operations both rely on credential misuse, we recommend enforcing phishing-resistant multifactor authentication (MFA) and strict least-privilege access, as this is the most effective way to disrupt the sequence of actions. Monitoring for unusual local activity, specifically anomalous access requests to the SAM database or unexpected behaviors originating including Windows Defender update processes—can help detect attempts and leverage the BlueHammer TOCTOU flaw before privilege escalation occurs. Furthermore, teams should prioritize the patching of CVE-2026-21509 and CVE-2023-23397 to neutralize the specific vectors currently favored by Russian state actors.

Infrastructure security must also extend to the network edge. Recent warnings from the FBI and NCSC regarding SOHO router modifications emphasize that remote management interfaces should be disabled and default credentials changed across all networking hardware. Applying firmware updates to TP-Link and MikroTik devices is a critical defensive measure against DNS hijacking. As unauthorized parties adjust their methodologies during geopolitical fluctuations, we work alongside organizations to reduce their external footprint and operate under the assumption of continuous external interest, which are highly effective ways to maintain resilience. The current environment demonstrates that while physical conflicts may pause during a ceasefire, digital reconnaissance and vulnerability utilization often become more focused.

While Microsoft has not yet released a formal patch for the BlueHammer race condition, they have updated Defender’s code to make the activity easier for defensive tools to detect. Security leaders should ensure their endpoint detection and response (EDR) signatures are current to catch these new detection patterns. At this stage, it remains unclear how reliably BlueHammer can be adapted for Windows Server environments. However, the rapid adaptation of the PoC by the research community suggests that more reliable variations of the technique are likely to emerge soon.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Evaluating threat actor activity during geopolitical ceasefires</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/716a12d0-d5db-4f25-89e3-12f4e27a057b</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/716a12d0-d5db-4f25-89e3-12f4e27a057b</guid>
        <pubDate>Fri, 10 Apr 2026 03:12:01 GMT</pubDate>
        <description>An analysis of historical data shows that military ceasefires rarely result in a decrease in malicious digital activity. Security leaders should maintain defensive readiness during geopolitical pauses, as threat actors often shift their focus to unauthorized cyber operations.</description>
        <content:encoded><![CDATA[
            With the United States and Iran reaching a fragile ceasefire this week, security researchers and executives are evaluating whether this will lead to a commensurate pause in the digital operations that have escalated alongside the conflict.

The day after the temporary truce was announced, Handala, one of Iran's most high-profile false-flag operations—stated it would participate in a temporary pause in hostilities. However, historical data suggests that truces rarely slow digital activity surrounding kinetic wars. In the absence of physical conflict, unauthorized digital operations tend to increase significantly.

"Historical data and recent intelligence analysis indicate that a military ceasefire rarely equates to a 'digital stand-down,'" notes Austin Warnick, director of Flashpoint’s National Security Intelligence Team. Speaking to Dark Reading, Warnick explained, "Cyber operations often remain steady or even flare up as an asymmetric pressure valve while kinetic hostilities are paused."

## Iran's Handala operation and the ceasefire

On April 8, Handala posted a notice to its Telegram channel conceding that "according to the orders from the highest leadership" in Iran, it has postponed its digital activity against the United States.

This development is notable given Handala's visibility. The group previously claimed responsibility for a ransomware-style incident affecting Stryker, one of the most high-profile targets for Iran to date—as well as unauthorized access to FBI director Kash Patel's personal email account.

Handala qualified its statement, noting that "The cyber war did not begin with the military conflict, and it will not end with any military ceasefire." The group indicated that its operations will eventually resume, and in the meantime, it will focus its efforts on Israeli targets.

Sergey Shykevich, threat intelligence group manager at Check Point Research, cautions that it is too early to determine whether Handala, or Iranian advanced persistent threats (APTs) in general, will reduce their activity. "I would not be surprised if, at some point over the next two weeks, they resume cyberattacks as another means of applying pressure against the US," Shykevich states.

## Threat actor responses to geopolitics

Politically motivated and false-flag threat groups often attempt to align themselves with ceasefire agreements, potentially seeking legitimacy by participating in a major geopolitical event. Whether their public commitments translate into action varies from conflict to conflict.

Following the October 7 events in Israel and the subsequent operations in Gaza, a temporary ceasefire was reached in late November 2023. At that time, Cyber Toufan, a false-flag operation aligned with Iran's "Resistance Axis," claimed it was pausing operations until kinetic conflict resumed. However, between November and December 2023, the group listed more than 100 affected Israeli organizations on its data leak site, making it unclear if their activity actually slowed.

Ceasefires frequently correlate with increased digital operations, as warring sides use alternative methods to apply pressure and gain leverage for future negotiations. For example, a Hamas-aligned threat actor used a 2021 ceasefire as an opportunity to launch a widespread phishing campaign across the Middle East. Similarly, when Ukraine and Russia agreed to a Black Sea ceasefire, both sides utilized the period to conduct major digital operations, including campaigns directed at the very energy infrastructure the ceasefire was intended to protect.

Markus Mueller, field CISO for Nozomi Networks, provides further historical context: "The major cyberattacks in Ukraine took place during a time when, at least on the Russian side, the war wasn't active. It was right after Russia annexed Crimea. They hadn't really done the big push... That in-between period is when we saw a lot of the larger attacks."

## Pivoting targets and maintaining vigilance

Threat actors often treat diplomatic pauses as technicalities. Warnick points out that groups use the time to pivot toward secondary targets or allies to maintain pressure without technically violating military agreements. Low-level digital activity from Iran-aligned groups such as the 313 Team and Conquerors Electronic Army has continued without interruption.

On April 8, the 313 Team claimed responsibility for an incident involving an Australian government authentication portal. Meanwhile, the Conquerors Electronic Army claimed distributed denial-of-service (DDoS) operations against Israeli targets and the US-based freelancer platform Upwork.

Mueller anticipates a shift in unauthorized activity in both scope and scale. "The majority of activity we've seen around this conflict so far is regionalized," he says. "We foresee. Based on what we've seen with other conflicts both within the region, but also with Ukraine—that it's going to grow a little more broad, and we're going to have more activity in North America, more activity in Europe, or any country that was seen as supporting the conflict."

Organizations should use these periods of geopolitical fluctuation to strengthen their defensive posture. Reviewing endpoint security configurations, implementing role-based access control (RBAC), and enforcing phishing-resistant multi-factor authentication (MFA) are critical steps to protect critical infrastructure and enterprise networks from pivoting threat actors.

While most ceasefires do not halt digital operations, the lead-up to the 2015 Iran nuclear deal provides a rare exception. Analysts initially observed the Islamic Republic probing US critical infrastructure for vulnerabilities. However, during the negotiating period, malicious online activity dropped completely. According to The New York Times, security researchers found not a single instance of a malicious phishing email or critical infrastructure probe directed at the US by Iran during that time. Unauthorized activity resumed slowly after negotiations ended, only reaching pre-negotiation levels after Donald Trump withdrew the United States from the agreement.

*Note: This analysis incorporates reporting by Nate Nelson, a journalist and scriptwriter for "Darknet Diaries." For more discussions on the evolving security scene, the Dark Reading Confidential podcast episode "Security Bosses Are All in on AI: Here's Why" features Reddit CISO Frederick Lee and Omdia analyst Dave Gruber examining the future of security products.*
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>BlueHammer Windows Zero-Day Surfaces Vulnerability Disclosure Challenges</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/42a92e06-92ae-45be-a1cb-a0c6f4d4b128</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/42a92e06-92ae-45be-a1cb-a0c6f4d4b128</guid>
        <pubDate>Fri, 10 Apr 2026 03:12:00 GMT</pubDate>
        <description>A recently published proof-of-concept for a Windows local privilege escalation vulnerability, known as BlueHammer, illustrates the complexities of coordinated disclosure. We examine the technical details of this TOCTOU flaw and provide guidance for securing environments while a formal patch is pending.</description>
        <content:encoded><![CDATA[
            On April 2, a security researcher operating under the alias "Chaotic Eclipse" published documentation and a GitHub repository containing proof-of-concept (PoC) code for an unpatched Windows vulnerability dubbed "BlueHammer." In the release, the researcher expressed frustration with Microsoft's timeline and response to the initial disclosure, questioning the Microsoft Security Response Center's (MSRC) decision-making process and noting that the flaw remained unpatched at the time of publication.

This friction reflects broader, systemic challenges within the security research community regarding vulnerability disclosure programs. Dustin Childs, head of threat awareness at Trend Micro's Zero Day Initiative (ZDI), noted that some researchers find the disclosure process frustrating and have stepped back from reporting Microsoft vulnerabilities as a result. Industry leaders, such as Tenable CEO Amit Yoran, have previously called for greater transparency from software vendors when managing vulnerabilities in cloud and enterprise environments.

In response to these industry-wide concerns, Microsoft has made vulnerability disclosure and transparency a core pillar of its Secure Future Initiative (SFI), launched in 2023. Recent progress reports highlight structural changes, such as the establishment of the Customer Security Management Office (CSMO) to improve public messaging and customer engagement during security incidents. Regarding the BlueHammer release, Microsoft affirmed its commitment to investigating reported security issues, updating affected devices, and supporting coordinated vulnerability disclosure to protect both customers and the research community.

## BlueHammer technical details

BlueHammer is a local privilege escalation (LPE) vulnerability. According to an advisory from the Retail & Hospitality-Information Sharing and Analysis Center (RH-ISAC), the flaw leverages a time-of-check to time-of-use (TOCTOU) race condition and path confusion within Windows Defender’s signature update mechanism.

The sequence of actions involves triggering a Defender signature update via Windows Update Agent COM interfaces, extracting a cabinet file, and forcing a write to a restricted path. If successfully executed by a local user, the technique provides access to the Security Account Manager (SAM) database via symbolic links and the Volume Shadow Copy Service. From there, an unauthorized party could extract password hashes and escalate to administrator rights using pass-the-hash techniques.

The vulnerability requires local access to the system and a running instance of Windows Defender. There is no known remote execution vector.

## Scope and current limitations

The original PoC published by Chaotic Eclipse contained acknowledged bugs that limited its reliability. However, a separate GitHub repository later provided a documented reimplementation, dubbed SNEK_BlueWarHammer—which includes complete Visual Studio build instructions and precompiled binaries, lowering the technical barrier for testing the flaw.

Security analysts, including Will Dormann of Tharros, note that the demonstration code primarily functions on Windows desktop systems and lacks reliability on Windows Server editions. Childs points out that server platforms contain different mitigations and access controls that disrupt the sequence. Furthermore, Chaotic Eclipse recently observed that while Microsoft has not yet patched the underlying bug, the vendor released a code update that makes the unauthorized activity slightly easier for defenders to detect.

## Securing environments

Because local privilege escalation requires an initial foothold on a device, organizations should prioritize foundational security practices while waiting for a formal patch. Threat actors actively monitor for public PoCs, and managed security service provider Cyderes warns that unauthorized parties often adapt these techniques rapidly for broader campaigns.

To safeguard systems, security teams should practice strict security hygiene. Enforcing the principle of least privilege across all Windows environments minimizes the risk that a standard user account can be compromised and used to trigger the TOCTOU flaw. Organizations should also monitor for unusual local activity, such as unexpected access requests to the SAM database or anomalous behaviors originating from Windows Defender update processes—and ensure employees are trained to recognize the social engineering tactics that often lead to initial credential compromise. By focusing on rapid detection and limiting local access, defenders can effectively mitigate the risk of unauthorized escalation.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Defending global infrastructure against APT28: Analysis of recent campaigns and mitigation strategies</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/fa919ba8-2ccb-456a-ab9d-7835139a0ca4</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/fa919ba8-2ccb-456a-ab9d-7835139a0ca4</guid>
        <pubDate>Fri, 10 Apr 2026 03:11:59 GMT</pubDate>
        <description>Recent intelligence details sustained campaigns by the APT28 threat actor targeting government, defense, and critical infrastructure networks. By understanding their use of specific vulnerabilities and router-based DNS redirection, security teams can implement targeted, foundational defenses to protect sensitive data.</description>
        <content:encoded><![CDATA[
            The advanced persistent threat (APT) group known as Fancy Bear and Forest Blizzard continues to target organizations globally. Linked to Russian military intelligence and active since the mid-2000s, the group consistently focuses on governments, defense supply chains, and critical infrastructure. Recent research from Trend Micro, alongside advisories from international security agencies, details the technical methodologies driving their current operations and offers a clear path for defenders to safeguard their networks.

## Malware components and vulnerability usage

Trend Micro recently published findings on two distinct APT28 operations. A March 26 report outlined a collection of malware components known as "Prismex," which the group has used to target the defense supply chains of Ukraine and its allies, including the Czech Republic, Poland, Romania, Slovakia, Slovenia, and Turkey. The campaign dates back to at least September 2025 and escalated in January 2026.

The Prismex suite relies on advanced steganography, component object model (COM) hijacking, and the abuse of legitimate cloud services for command and control. The malware includes both espionage functions and destructive sabotage capabilities. To deploy Prismex, the threat actor leverages multiple Windows vulnerabilities, notably CVE-2026-21513, a zero-day vulnerability in the MSHTML framework, and CVE-2026-21509, a Microsoft Office Object Linking and Embedding (OLE) bug.

A separate report detailed the group's use of NTLMv2 hash relay operations between April 2022 and November 2023. In these campaigns, APT28 sent malicious calendar invites via.msg files, capitalizing on CVE-2023-23397, a critical patched vulnerability in Microsoft Outlook. When triggered, the connection forwards the user's Net-NTLMv2 hash to an external Server Message Block (SMB) server. This allows the unauthorized party to authenticate against other systems that support NTLM without requiring the user's actual password.

To obscure their origin during these operations, the group utilized virtual private networks (VPNs), Tor, data center IP addresses, and compromised routers. Feike Hacquebord, a principal threat researcher at TrendAI, noted that the group effectively blends novel methods with decades-old techniques, targeting both high-profile defense ministries and smaller entities like local municipal governments.

## Router compromise and DNS redirection

Complementing the malware findings, the FBI and the UK's National Cyber Security Centre (NCSC) issued warnings regarding the group's abuse of small-office home-office (SOHO) routers to help credential theft.

Specifically targeting devices such as TP-Link routers through CVE-2023-50224, as well as MikroTik and EdgeOS systems, the actor alters the devices' Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) settings. This routes traffic through unauthorized DNS resolvers, facilitating adversary-in-the-middle (AitM) operations against encrypted communications. If users click past certificate error warnings, the actor can capture sensitive credentials and OAuth tokens.

In response to this activity, the FBI and the US Department of Justice recently disrupted a network of these compromised SOHO routers to halt the DNS hijacking operations.

## Implementing effective defenses

Defending against a well-resourced APT requires a focus on security fundamentals. Denis Calderone, CTO of Suzu Labs, advises that while APT28 exhibits sophisticated post-access tradecraft, their initial access heavily relies on common methods like phishing, weak credentials, and known vulnerabilities.

Foundational practices provide significant protection against these vectors:
* Enforcing multifactor authentication (MFA) prevents password spraying and unauthorized credential reuse.

* Patching Microsoft Office and Windows environments mitigates the risk of vulnerabilities like CVE-2026-21509 and CVE-2023-23397.

* Applying router firmware updates, disabling remote management interfaces, and changing default credentials neutralizes hardware-level initial access.

* Conducting ongoing user awareness training reduces the risk of social engineering, such as recognizing deceptive CAPTCHA prompts used in initial access campaigns.

For defense in depth, Vishal Agarwal, CTO of Averlon, recommends implementing zero trust architecture, least-privilege access, strong identity controls, and just-in-time access. These measures severely restrict lateral movement if an initial boundary is bypassed.

Seemant Sehgal, CEO of BreachLock, adds that organizations improve their resilience by continually reducing their external footprint and operating under the assumption that they are a target. By maintaining strong foundational controls and rigorous identity management, security teams deny threat actors the straightforward pathways they rely on, making unauthorized access significantly more difficult to achieve.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Shift to Edge Device Compromise and Malware-Less Interception Outpaces Traditional Detection</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/fbfcaf6d-ef96-41e8-b719-d40bee4df4ae</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/fbfcaf6d-ef96-41e8-b719-d40bee4df4ae</guid>
        <pubDate>Thu, 09 Apr 2026 03:17:04 GMT</pubDate>
        <description>Recent data confirms a systemic shift in how state-affiliated actors bypass traditional endpoint detection, focusing on internet-exposed edge devices like SOHO routers and industrial control systems. This analysis details the mechanics of these malware-less interception campaigns and provides actionable guidance on hardware lifecycle management and behavioral monitoring to secure network boundaries.</description>
        <content:encoded><![CDATA[
            Security teams are navigating a environment where the primary challenge extends beyond sophisticated malware to the unauthorized reconfiguration of the foundational infrastructure routing our traffic and managing critical services. Recent data shows a widespread campaign by the Russian state-sponsored group APT28, which intercepted global internet traffic for over a year by modifying the DNS settings on unmanaged small office and home office (SOHO) routers. This activity, which led to a U.S. Department of Justice disruption effort named "Operation Masquerade" on April 7, 2026, confirms a shift toward passive, malware-less interception that bypasses traditional endpoint detection.

This focus on internet-exposed edge devices extends beyond Russian operations. CISA and partner federal agencies recently issued a joint advisory regarding Iran-affiliated threat actors, likely the CyberAv3ngers or Shahid Kaveh Group—accessing programmable logic controllers (PLCs) across U.S. critical infrastructure. Similar to the APT28 campaign, these groups are using internet-exposed hardware, specifically Rockwell Automation and Allen-Bradley PLCs, to disrupt operations in the energy and water sectors. Both campaigns reveal a persistent systemic weakness: the continued exposure of administrative interfaces on the public internet and a lack of visibility into hardware at the network edge.

The APT28 campaign, also tracked as Forest Blizzard or Fancy Bear, demonstrates significant tactical adaptability. While the group historically relied on custom malicious software, this recent operation involves reconfiguring MikroTik, TP-Link, and Fortinet routers to direct DNS traffic through unauthorized virtual private servers. By the end of 2025, this infrastructure communicated with 18,000 unique IP addresses across 120 countries. The objective focuses almost entirely on credential harvesting. By controlling DNS resolution, the unauthorized parties proxy authentication requests for services like Microsoft Outlook on the Web, capturing logins in an Adversary-in-the-Middle (AiTM) configuration without accessing the affected organization's internal network. This methodology makes detection difficult because there is no malicious file to scan, only a modified configuration entry on a device that rarely supports detailed logging.

Technical details including the Iran-affiliated activity against PLCs show a similar reliance on common configuration tools. These actors utilize software like Rockwell Automation’s Studio 5000 Logix Designer to connect and target PLCs over ports such as 44818, 2222, and 502. The advisory notes the actors successfully manipulated PLC project files and altered HMI displays, creating a risk of physical operational disruptions. In some instances, the actors deployed Dropbear SSH on these endpoints to maintain persistence via port 22. This demonstrates that once an edge device—whether a SOHO router or an industrial controller. Is accessed via an exposed management port, the unauthorized user gains a potential gateway to the rest of the environment.

The challenge of detecting unauthorized activity is complicated further by creative uses of visual language. Recent analysis indicates threat actors increasingly use emojis to obfuscate command-and-control (C2) operations and coordinate on platforms like Telegram and Discord. The Pakistan-linked group UTA0137, for example, uses a tool called "Disgomoji" to translate specific symbols into commands: a fire emoji initiates a file transfer, while a skull emoji terminates a process. This "emoji smuggling" allows unauthorized instructions to bypass legacy keyword filters that search exclusively for text-based triggers. It reflects a broader shift toward faster, visual communication that mimics benign user behavior to hide in plain sight.

As automated scanning and AI accelerate vulnerability discovery, the defensive community faces significant constraints in remediation capacity. HackerOne recently paused new submissions to its Internet Bug Bounty (IBB) program, citing a massive imbalance between the volume of AI-generated vulnerability reports and the capacity of open-source maintainers to patch them. Security triage teams report that while the volume of submissions has skyrocketed, the signal-to-noise ratio has plummeted, with valid reports dropping from 15% to below 5%. This fatigue is particularly acute for volunteer-driven projects like Node.js, which paused its own bounty program after losing IBB funding. It reveals a critical gap in the current security ecosystem: the industry has become highly efficient at finding flaws, but lacks the structural funding to fix them at the same speed.

For defenders, these developments require a pivot toward behavioral monitoring and strict hardware lifecycle management. To protect against DNS redirection and unauthorized PLC access, the first priority is eliminating internet-exposed management interfaces. Organizations must verify that PLCs sit behind secure firewalls and, where possible, place physical mode switches on controllers into the "run" position to prevent unauthorized programmatic changes. For SOHO and remote-office hardware, security teams need to move beyond "set and forget" deployments. This includes replacing end-of-life devices that no longer receive security updates and implementing Zero Trust DNS controls to ensure resolvers are not silently redirected at the router level.

Monitoring strategies must also evolve to account for the lack of traditional signatures. Detecting APT28’s activity or emoji-based C2 requires looking for "living-off-the-land" anomalies, such as unusual outbound traffic to overseas hosting providers on ports 44818 or 502, or unexpected Unicode characters in script logs. In the mobile-first environment, particularly in regions like Latin America where banking fraud surged by 155% through social engineering and remote-access tools, the focus needs to shift toward identity and behavioral context. Relying on a single factor of authentication is insufficient when unauthorized actors can bypass it by controlling the underlying device or its DNS infrastructure.

The primary takeaway from today’s scene is the rapid scaling of the initial phases of the compromise lifecycle. AI accelerates the discovery of vulnerabilities, and automation allows state-affiliated actors to scan for and access edge devices globally. However, the human-led processes of patching, triage, and network hardening are struggling to keep pace. The current shift toward malware-less interception and symbolic C2 suggests that the next phase of defense will rely less on finding malicious files and more on verifying the integrity of system configurations and the authenticity of digital routes. While the full extent of the data harvested during the year-long APT28 router campaign remains uncertain—as much of the traffic was likely encrypted, the efficacy of AiTM techniques against web-based mail services remains a significant concern for global organizations.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Advisory: Threat actors target internet-exposed PLCs in US critical infrastructure</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/144c8403-93aa-4d28-ba2b-72fd910c5b4e</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/144c8403-93aa-4d28-ba2b-72fd910c5b4e</guid>
        <pubDate>Thu, 09 Apr 2026 03:17:03 GMT</pubDate>
        <description>CISA and partner federal agencies have issued a joint advisory detailing unauthorized access to internet-exposed programmable logic controllers (PLCs) across multiple critical infrastructure sectors. The guidance outlines the specific operational technology (OT) devices targeted and provides immediate remediation steps to help organizations secure their environments.</description>
        <content:encoded><![CDATA[
            Iran-affiliated threat actors are conducting unauthorized campaigns against US critical infrastructure by targeting internet-exposed operational technology (OT) devices. The activity spans multiple sectors, including energy, water and wastewater, and government facilities.

This security alert coincides with recent geopolitical developments, emerging shortly before a tentative ceasefire agreement in the ongoing conflict between the US and Iran. The campaign, which began following recent military engagements involving the US, Israel, and Iran, focuses primarily on programmable logic controllers (PLCs). According to a joint advisory from the Cybersecurity and Infrastructure Security Agency (CISA), the FBI, NSA, EPA and the Cyber National Mission Force (CNMF), Rockwell Automation and Allen-Bradley PLCs are the primary devices impacted.

The federal agencies report that these unauthorized actions have resulted in operational disruptions and financial losses for some affected organizations. The threat actors successfully manipulated PLC project files and altered supervisory control and data acquisition (SCADA) and human-machine interface (HMI) displays.

While the agencies did not explicitly name the specific group responsible for the current activity, they noted that the methodology aligns with previous campaigns by CyberAv3ngers (also known as the Shahid Kaveh Group), a threat actor affiliated with Iran's Islamic Revolutionary Guard Corps (IRGC) Cyber Electronic Command. In November 2023, this group gained unauthorized access to at least 75 US-based Unitronics PLC devices equipped with HMIs across various critical infrastructure sectors.

## Internet-facing devices accessed

The joint advisory provides specific technical details on how the threat actors connect to internet-facing Rockwell Automation and Allen-Bradley PLCs. The actors utilize leased, third-party-hosted infrastructure located overseas and leverage configuration tools, such as Rockwell Automation's Studio 5000 Logix Designer software, to establish accepted connections to the target PLCs. The documented activity specifically involved CompactLogix and Micro850 PLC devices.

Network traffic was directed to these devices via ports 44818, 2222, 102, 22, and 502, as well as port T0885. The inclusion of port T0885 indicates that the threat actors may also be scanning for or targeting other hardware, such as the Siemens S7 PLC.

Additionally, the advisory notes that the actors deployed Dropbear Secure Shell (SSH) software on affected endpoints to maintain remote access through port 22.

## Apply mitigations now

Given the history of targeted activity against US critical infrastructure and the current geopolitical climate, federal agencies strongly recommend that facilities implement immediate defensive measures. Gabrielle Hempel, a security operations strategist at Exabeam, emphasizes that the core issue is structural rather than strictly threat-based.

"If an OT environment is reachable from the Internet, that is an inherent design flaw and not a nation-state problem," Hempel states.

To help critical infrastructure organizations secure their networks, CISA and the partner agencies recommend the following immediate actions:

* Remove internet exposure: Isolate PLCs from the public internet and place them behind secure gateways and firewalls.

* Monitor network traffic: Review available logs for suspicious traffic on ports associated with OT devices—specifically 44818, 2222, 102, and 502—with particular attention to traffic originating from overseas hosting providers.

* Review indicators of compromise: Search network logs for the specific IOCs provided in the CISA advisory matching the corresponding time frames.

* Secure physical controllers: For Rockwell Automation and Allen-Bradley devices, place the physical mode switch on the controller into the "run" position to prevent unauthorized programmatic changes.

Organizations that suspect their devices may have been impacted should contact the authoring agencies and Rockwell Automation for guidance and support.

*(Based on original reporting by Elizabeth Montalbano).*
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Analyzing the Increase in Mobile-First Banking Fraud Across Latin America</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/924ede82-849b-45fb-a8a4-8900e82f57dc</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/924ede82-849b-45fb-a8a4-8900e82f57dc</guid>
        <pubDate>Thu, 09 Apr 2026 03:17:03 GMT</pubDate>
        <description>Digital banking fraud across Latin America is accelerating due to a shift toward mobile-focused security incidents and social engineering. This analysis outlines the methodologies threat actors are using to bypass authentication and the collaborative defensive measures organizations can implement to protect users.</description>
        <content:encoded><![CDATA[
            Digital banking fraud across Latin America has seen a measurable increase, currently outpacing other global regions. This trend is primarily driven by elevated rates of social engineering, unauthorized account access, and mobile-focused security incidents.

According to a 2025 report published by fraud and financial-crime prevention firm BioCatch, social engineering attempts increased by 155% in the region. The data also indicates sharp climbs in malware, remote-access fraud, and unauthorized access stemming from stolen devices. These metrics indicate a structural shift in methodologies, where threat actors increasingly chain techniques together, moving from voice-based scams to account takeover (ATO), and ultimately to unauthorized financial transfers.

Josué Martínez, senior director of global advisory for Latin America at BioCatch, notes that gaining physical or remote access to a device enables unauthorized parties to initiate a sequence of actions resulting in misdirected funds.

"We are seeing continuous evolution in attackers' methods, with tactics that increasingly target and undermine authentication layers rather than individual transactions," Martínez says. "As a result, traditional controls are often insufficient on their own."

Organizations in Latin America currently experience approximately 50% more security incidents than the global average. Over the past year, specific threat groups—including Vixen Panda, Aquatic Panda, and Liminal Panda. Have focused on government agencies, telecom providers, and military entities in the region. Concurrently, Brazilian threat actors recently deployed a banking Trojan designed to automatically collect banking credentials from consumers.

The impact of these trends varies by country. Mexico observed a 300% increase in account takeover attempts, while Colombia experienced broader increases across phishing, SIM swapping, and malware. Conversely, Argentina recorded a decline in mule account activity following the implementation of a real-time fraud intelligence-sharing network, demonstrating how coordinated defensive measures effectively shift outcomes and reduce risk.

## Fraud driven by a mobile-first economy

Part of the challenge for financial institutions involves regional liability frameworks. When governments do not consistently hold banks liable for fraud losses, institutions may face less immediate financial incentive to prioritize preventative cybersecurity controls.

"In many countries, scam-related losses are not consistently reimbursed by financial institutions, which reduces the immediate financial incentive to invest aggressively in preventative controls focused on social engineering," Martínez says. "At the same time, rapid digital adoption — often driven by mobile-first users and real-time payments, has expanded the number of less-experienced digital consumers, creating a larger and more attractive pool of potential victims."

Account-takeover incidents are increasing, with Mexican banks seeing a fourfold increase in 2025, and the broader region encountering 1.6 times more incidents. Mobile devices are the primary focus because controlling the device often allows a threat actor to bypass second-factor authentication and proceed with an ATO.

"The majority of users rely on Android devices, [and] the widespread availability of remote-access tools for this operating system drives a higher incidence of these scams, which are frequently used in multiple ways to defraud users," Martínez adds.

Late last year, Chinese-speaking threat actors focused on the region with a banking bot dubbed ToxicPanda, which attempted to compromise accounts at 16 different financial institutions. In March, an Android-based banking Trojan targeted Brazil's Pix mobile payment network, deceiving users into installing software that remained dormant on the device until it could intercept and redirect payments.

## Regional variations in fraud patterns

While each country in Latin America manages a distinct threat profile, the focus on mobile environments extends across the region. BioCatch reports a 340% year-over-year increase in stolen devices in Brazil. Colombia sees smaller increases in device theft but faces elevated rates of SIM swapping and mobile malware. Additionally, the deployment of remote access Trojans (RATs) targeting mobile devices rose during the latter half of 2025.

Argentina's reduction in money-mule accounts in late 2025 stands out as a positive departure from regional averages. However, when organizations effectively mitigate a specific methodology, unauthorized parties adapt quickly.

"Once banks in a given country have effectively solved for a particular MO, fraudsters will either change MOs or shift their focus to a different geography," Martínez says.

To stay ahead of these shifts, organizations must move beyond static defenses and prioritize collaboration. Technical controls work best when paired with broader context.

"Technical controls must be complemented by additional capabilities that provide broader context, such as consortium-based intelligence that helps assess the risk reputation of the target account," Martínez says. "This layered approach allows institutions to move beyond isolated signals and develop a more accurate understanding of intent and exposure."

*(Original reporting by Robert Lemos, contributing writer and veteran technology journalist.)*
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>HackerOne Pauses Internet Bug Bounty to Address AI-Driven Remediation Imbalance</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/2dce49f0-4173-4dba-89e9-2091b66a5590</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/2dce49f0-4173-4dba-89e9-2091b66a5590</guid>
        <pubDate>Thu, 09 Apr 2026 03:17:02 GMT</pubDate>
        <description>The rapid adoption of AI in vulnerability research has significantly increased the volume of security reports, straining the capacity of open-source maintainers. In response, industry leaders are reevaluating vulnerability programs to better support triage and fund remediation efforts.</description>
        <content:encoded><![CDATA[
            HackerOne recently paused new vulnerability submissions to its crowdsourced Internet Bug Bounty (IBB) program, surfacing a systemic challenge in the software industry: the growing disparity between AI-assisted vulnerability discovery and the capacity of open-source maintainers to remediate those findings.

Operating since 2013, the IBB serves as a primary vulnerability reward program for the open-source ecosystem. On March 27, HackerOne suspended new submissions, citing a significant imbalance between the volume of reported vulnerabilities and the available resources for maintainers to process and patch them.

## Signal versus noise in automated reporting

"The discovery situation is changing. AI-assisted research is expanding vulnerability discovery across the ecosystem, increasing both coverage and speed," HackerOne announced. The organization noted that the balance between findings and remediation capacity has shifted substantially, requiring a reassessment of the structure and incentives of crowdsourced programs like the IBB.

Following the IBB suspension, maintainers of the open-source Node.js project paused their own security reward program due to the loss of IBB funding. As a volunteer-driven project, Node.js maintainers explained they lack an independent budget to sustain monetary rewards.

Security practitioners view this shift as a predictable outcome of integrating AI into vulnerability research. Ensar Seker, chief information security officer at SOCRadar, describes the pause as a rational correction to how vulnerability ecosystems operate under the pressure of automated generation.

"HackerOne is essentially acknowledging that the bottleneck has shifted: discovery has been industrialized by AI, but remediation capacity has not scaled accordingly," Seker says. When automated tools generate thousands of low- to medium-quality findings in a short period, volunteer maintainers with limited funding quickly reach capacity. Seker adds that the pause is an attempt to rebalance signal versus noise rather than a reduction in security commitment.

## The impact on validation and triage

The increase in automated submissions has directly affected the validation process. John Morello, co-founder and chief technology officer of Minimus, notes that the rate of valid submissions dropped from approximately 15% to below 5% as triage queues filled with low-quality automated reports.

"AI-assisted hunting hasn't necessarily found more critical zero-days; instead, it's shifted the bottleneck entirely to validation, forcing triage teams to wade through thousands of plausible-sounding but non-exploitable reports," Morello says.

For open-source maintainers, this validation bottleneck results in "triage fatigue," consuming development hours to disprove hallucinated vulnerabilities. "The current bounty model unfortunately rewards quantity over depth, effectively weaponizing unpaid labor and forcing these small teams to act as a free quality assurance department for every automated scanner on the planet," Morello notes.

## Balancing discovery and remediation

HackerOne is currently evaluating new approaches with project maintainers and researchers to align incentives and ensure vulnerability discoveries lead to durable security improvements.

Trey Ford, chief strategy and trust officer at Bugcrowd, views the situation as an indicator that the industry has spent years optimizing the wrong end of the security pipeline. AI successfully compressed the time required to find vulnerabilities, but the operational challenge of a maintainer receiving 40 valid reports with limited time to respond remains unsolved.

Because AI lowers the barrier to initial discovery, raw volume no longer offers a competitive advantage for researchers. Ford anticipates that value will increasingly shift toward identifying complex logic flaws and novel sequences of actions that require human depth and contextual judgment. "The next generation of vulnerability programs may offer bonuses to researchers for bringing fixes, not just reporting vulnerabilities, and create shared pools that fund both the researcher who finds and the maintainer team that ships the patch," he says.

Reward programs originally designed around human-paced research are also depleting funds faster than anticipated. David Hayes, VP of product at FusionAuth, notes that the current model requires structural changes to remain sustainable. Programs were built for an environment where discovery was the primary bottleneck. Now that discovery is heavily automated, the bottleneck is remediation—a phase that traditional programs do not fund.

"The projects that underpin critical Internet infrastructure can't rely on volunteer labor to process AI-generated reports at scale," Hayes says. "The industry needs to figure out how to fund the fix, not just the find."

***

*Original reporting by Jai Vijayan, a technology reporter with over 20 years of experience covering information security, data privacy, and data analytics.*
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Analyzing the Use of Emojis in Threat Actor Communications and Command Operations</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/2852eff7-de9e-4eaa-9881-71b280d8f232</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/2852eff7-de9e-4eaa-9881-71b280d8f232</guid>
        <pubDate>Thu, 09 Apr 2026 03:17:02 GMT</pubDate>
        <description>Threat actors increasingly use emojis to obfuscate communications, coordinate unauthorized access, and execute command-and-control operations. By understanding these visual patterns and implementing behavioral detection, security teams can better identify hidden instructions and track decentralized threat activity.</description>
        <content:encoded><![CDATA[
            Emojis serve a functional purpose for threat actors operating across digital messaging platforms and underground communities. On platforms like Telegram and Discord, these symbols are increasingly used to signal intent, coordinate actions, and obfuscate communications from automated monitoring systems.

A visual shift in communication

"Emoji usage reflects a broader shift in how threat actors communicate toward faster, more visual, and more adaptive forms of interaction," Flashpoint noted in a recent analysis. Incorporating emoji analysis into threat intelligence workflows allows organizations to better detect emerging campaigns, attribute malicious activity, and interpret the intent of unauthorized parties. While emojis alone are not definitive indicators of compromise, they provide a valuable layer of signal that strengthens overall security analysis.

Threat actors frequently use the benign appearance of emojis to conceal command-and-control (C2) communications and bypass legacy keyword filters. By replacing common risk-associated keywords with symbols, malicious actors reduce their visibility in automated environments. Additionally, emojis enable more effective multilingual communication, allowing decentralized global networks to coordinate without relying on a shared spoken language.

Command operations and code concealment

In one documented campaign, the Pakistan-linked advanced persistent threat (APT) group UTA0137 used "Disgomoji," a malicious tool that translates simple emojis sent over Discord into operational commands. Examples of these symbolic triggers included a camera emoji to capture screenshots, a fire emoji to transfer files, and a skull emoji to terminate processes.

Other security researchers have observed the emergence of emoji-based C2 operations where common symbols are repurposed to confirm task completion and orchestrate data movement across compromised systems. This extends to "emoji smuggling" techniques, where threat actors embed unauthorized instructions within standard Unicode characters. Because these characters are processed normally by the operating system, the malicious code can bypass traditional security controls that only look for known malware signatures.

Common use cases

According to Flashpoint's analysis, threat actors commonly use emojis to categorize activities related to financial fraud, credential access, and service capabilities. Common patterns include:

* Financial activity: A card symbol often indicates stolen payment data, while a bag of money signals successful monetization or payouts.

* Access and credentials: A key typically represents access credentials, and an open lock signals successful unauthorized access to a target system.

* Tooling and capabilities: A robot emoji is frequently used to advertise bot services or automation tools, a gear cog indicates infrastructure setup, and a toolbox denotes bundled services.

* Targeting: Building emojis often indicate corporate or enterprise targets, while country flags specify geographic focus.

When these symbols are combined with industry slang and multilingual phrasing, they create a layered form of obfuscation that complicates large-scale monitoring efforts.

Tracking and defense methodologies

Because emoji usage tends to follow recognizable behavioral patterns over time, security researchers and threat hunters can use these sequences to track malicious actors. Consistent combinations of emojis in sales posts, specific formatting styles, and repeating message structures act as lightweight identifiers. These patterns enable analysts to link a threat actor's activity across different channels, platforms, and aliases.

To protect organizations from Unicode-based concealment and emoji smuggling, security teams should look beyond traditional signature-based detection. Effective defensive measures include:

* Behavioral analysis: Implement Endpoint Detection and Response (EDR) or Extended Detection and Response (XDR) solutions that monitor for suspicious activity, such as unauthorized file encryption or unusual network connections, regardless of how the initial code is formatted.

* Advanced email security: Deploy multi-layered filtering that analyzes file behavior and Unicode anomalies rather than relying solely on known malicious attachment signatures.

* Continuous security monitoring: Pair automated alerts with active monitoring by security analysts who can investigate unusual network behavior and contain threats in real time.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>APT28 Leverages SOHO Routers for Global DNS Redirection and Credential Harvesting</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/1977ef27-8c18-4897-8677-7f5ee3ee6cde</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/1977ef27-8c18-4897-8677-7f5ee3ee6cde</guid>
        <pubDate>Thu, 09 Apr 2026 03:17:01 GMT</pubDate>
        <description>A Russian state-sponsored threat group has intercepted global internet traffic for over a year by modifying DNS settings on unmanaged small office and home office (SOHO) routers. This methodology allows the group to passively monitor web requests and harvest credentials without deploying traditional malware.</description>
        <content:encoded><![CDATA[
            A state-sponsored threat group operating out of Russia has been passively intercepting internet traffic from global targets for over a year. The group achieves this by leveraging known vulnerabilities in internet-exposed small office/home office (SOHO) routers. Affected entities include foreign affairs ministries and national law enforcement bodies in North Africa, Central America, and Southeast Asia, as well as a national identity platform, European service providers, and organizations across 23 US states.

Advanced persistent threats often rely on complex evasion techniques or undisclosed vulnerabilities. However, the group tracked as APT28 (also known as Forest Blizzard, Fancy Bear, or Storm-2754) has demonstrated that simpler methods remain highly effective for broad data collection.

Since at least May 2024, the group has intercepted traffic at high-value organizations by accessing edge devices—primarily MikroTik and TP-Link routers, alongside select Nethesis and Fortinet products. Rather than deploying traditional malware, the threat actors reconfigure the routers to direct Domain Name System (DNS) traffic through unauthorized virtual private servers (VPS). According to researchers at Microsoft and Lumen’s Black Lotus Labs, this methodology allows the group to passively monitor web traffic and harvest credentials for email and web services.

At its peak in December 2025, Black Lotus Labs observed 18,000 unique IP addresses across 120 countries communicating with the unauthorized infrastructure. Microsoft identified more than 200 impacted organizations and over 5,000 consumer devices.

APT28’s primary objective in this campaign is email compromise, continuing a historical pattern of targeting organizational and individual communications. The group scans for known flaws, such as CVE-2023-50224, a medium-severity information disclosure issue in TP-Link devices that allows unauthenticated remote administration. Once accessed, the group modifies the router's DNS settings. When a user navigates to a targeted service—such as Microsoft Outlook on the Web—the modified DNS proxies the request. This Adversary-in-the-Middle (AiTM) technique captures user credentials during the authentication process.

"One of the things that piqued my interest: there is no malware," notes Danny Adamitis, principal information security engineer at Black Lotus Labs. "If you were to have your router getting logged into, even if you were to hypothetically scan it all with an endpoint detection and response (EDR) tool or upload everything to VirusTotal, there is nothing there. The only thing they're doing is modifying just one entry of your DNS settings, to route traffic to a server that they control and administrate."

Security researchers note varying start dates for the activity. Microsoft telemetry indicates August 2025, while Black Lotus Labs identified a compromised router associated with the government of Afghanistan in May 2024. The US Department of Justice (DOJ) states the activity dates to at least 2024. Regardless of the exact start, the group demonstrated high adaptability. On August 6, 2025, the UK’s National Cyber Security Centre (NCSC) published "Authentic Antics," a report detailing an APT28 tool used to capture Microsoft Office credentials. The following day, the group shifted its tactics entirely toward the SOHO router campaign.

On April 7, 2026, the DOJ announced "Operation Masquerade," a court-ordered disruption effort aimed at securing the US-based portion of the compromised infrastructure. The operation involved sending commands to affected TP-Link routers to collect forensic data and reset DNS configurations, effectively pointing the devices back to legitimate Internet Service Provider (ISP) resolvers.

Ryan English, information security engineer at Lumen Technologies, observes that while organizations should transition away from SOHO routers, their prevalence is understandable. "It's a question of economics, convenience, and access," English explains. "Some governments might make the choice to use this because it works perfectly well. But you can't inspect the logs on a lot of these SOHO routers. Some of them are not easy to manually update whenever there's patching needed. So they're vulnerable as sort of a condition of their existence."

Adamitis points to a broader systemic issue with DNS trust. He compares DNS to mapping software: users implicitly trust the route provided without verifying the underlying data. "Users trust that DNS can tell you where your server is," he notes. APT28 alters that routing on the back end. While router ecosystems offer patching and maintenance mechanisms, Adamitis describes DNS as a decentralized system lacking clear accountability. "It truly is, in my mind, the Wild West."

To protect networks against DNS redirection and edge device compromise, organizations and remote personnel should prioritize hardware lifecycle management. Security teams recommend replacing end-of-life routers, applying the latest firmware updates, and verifying the authenticity of DNS resolvers in device settings. Additionally, implementing strict firewall rules to restrict remote management services and utilizing Zero Trust DNS controls can significantly reduce the risk of unauthorized traffic interception.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Securing the Network Perimeter Against High-Velocity Threats and AI Vulnerabilities</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/f20b76cf-82c5-4c47-b3c7-634fb98957cf</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/f20b76cf-82c5-4c47-b3c7-634fb98957cf</guid>
        <pubDate>Wed, 08 Apr 2026 03:07:02 GMT</pubDate>
        <description>With malicious actors reducing their vulnerability targeting cycles to mere hours, security teams face growing pressure to rapidly secure perimeter assets. This briefing examines the swift methodologies of groups like Storm-1175, details emerging AI prompt injection risks in tools like Grafana, and provides concrete hardening guidance to protect organizational infrastructure.</description>
        <content:encoded><![CDATA[
            The operational window for security teams to address new vulnerabilities is frequently measured in hours rather than weeks or days. The current environment involves continuous pressure from financially motivated malicious actors who have optimized their workflows to identify and target exposed perimeter assets. A primary example is the group tracked as Storm-1175. This group rapidly utilizes newly disclosed vulnerabilities to deploy Medusa ransomware, occasionally completing the sequence from initial access to data exfiltration in under 24 hours.

This compressed timeline, documented in recent reports from Microsoft Threat Intelligence and industry researchers, marks a shift in how ransomware groups interact with the vulnerability management lifecycle. Storm-1175 does not solely rely on public disclosures. In several instances, the group has leveraged zero-day vulnerabilities at least a week before public acknowledgment. This operational pace indicates the group may possess advanced internal development capabilities or access to specialized vulnerability brokers, enabling them to move faster than the standard patching cycles of many enterprise organizations.

These high-velocity campaigns have primarily affected the healthcare, education, professional services, and finance sectors, specifically within the United States, United Kingdom, and Australia. By targeting critical vulnerabilities in web-facing infrastructure, including remote support tools and file transfer software—Storm-1175 bypasses the traditional phishing-based entry methods that many security programs monitor. Instead, the group focuses on direct unauthorized access through the network perimeter.

While Storm-1175 illustrates the risk of rapid vulnerability targeting in traditional software, the integration of artificial intelligence introduces a different category of exposure. Security researchers recently identified a prompt injection vulnerability in Grafana’s AI assistant, designated "GrafanaGhost," which could have allowed unauthorized parties to access sensitive telemetry or financial data. Grafana has since patched the issue, but the discovery shows that as organizations adopt AI components to manage their environments, they inadvertently expand their digital footprint. This expansion includes risks like indirect prompt injection, a technique where unsafe instructions are hidden in data the AI processes.

From a technical standpoint, Storm-1175 operates with notable efficiency. Their recent activity includes the rapid targeting of CVE-2026-1731, a critical remote code execution vulnerability in BeyondTrust Remote Support. The group targeted this flaw almost immediately following its February 6 disclosure, leading to its inclusion in CISA’s Known Exploited Vulnerabilities (KEV) catalog just a week later. The group's "N-day" toolset is extensive, covering critical flaws in CrushFTP (CVE-2025-31161), JetBrains TeamCity (CVE-2024-27198), and older Microsoft Exchange vulnerabilities (CVE-2023-21529) that remain unpatched in various environments.

The group's use of undisclosed vulnerabilities presents a more complex challenge for defensive teams. Researchers linked Storm-1175 to the targeting of CVE-2026-23760, an authentication bypass in SmarterMail, and CVE-2025-10035, a maximum-severity flaw in GoAnywhere Managed File Transfer. In both instances, the group was active approximately seven days before public awareness of the issues. Once initial access is secured, the group follows a standardized sequence: they deploy legitimate remote monitoring and management (RMM) tools for lateral movement, use the Impacket framework for credential extraction, and utilize Rclone for data transfer before deploying ransomware.

A key technical component of the Medusa deployment is the group’s focus on security tampering. Storm-1175 actors modify Windows registry settings to interfere with Microsoft Defender Antivirus, effectively disabling endpoint detection so the ransomware can run unhindered. This technique requires highly privileged access, which makes the credential extraction phase, specifically the use of Impacket—a vital intervention point for defensive teams seeking to protect their environments.

The GrafanaGhost vulnerability details a different mechanism for unauthorized access. Researchers at Noma Security found they could bypass Grafana's image rendering protections by using protocol-relative URLs and a specific "INTENT" keyword within image tags. By placing these unintended instructions in a location the AI assistant naturally retrieves. Such as an entry log—the researchers could cause the AI to send sensitive data to an external server. There is a discrepancy between the researchers and the vendor regarding the interaction requirements for this flaw. Grafana Labs states that significant user interaction was necessary to trigger the bug, whereas the researchers report that the AI processed the instructions autonomously. Regardless of the interaction requirements, the core issue was remediated through a patch to Grafana’s Markdown renderer.

To protect their organizations, security teams must reduce the "mean time to patch" (MTTP) for critical perimeter assets to the absolute minimum. When a critical remote code execution or authentication bypass flaw is disclosed in a web-facing service, we recommend prioritizing the patch immediately, often within the same business day. This rapid response helps organizations stay ahead of the 24-hour targeting cycle observed in Storm-1175 operations.

Beyond patching, infrastructure hardening is essential for comprehensive protection. Organizations should prioritize the isolation of web-facing systems, placing any necessary public servers behind a Web Application Firewall (WAF) or within a strictly segmented DMZ. To counter the specific tampering techniques seen in Medusa deployments, security teams should enable Windows Defender Antivirus tamper protection and apply the `DisableLocalAdminMerge` setting. This configuration prevents malicious actors including using local admin privileges and establish antivirus exclusions. Furthermore, implementing Windows Credential Guard helps protect process memory including the credential extraction methods that Storm-1175 relies on to gain the privileges necessary for security tampering.

The high-tempo operations of Storm-1175 indicate that ransomware groups are increasingly mirroring the capabilities of state-sponsored actors in their ability to operationalize vulnerabilities. This structured approach and vulnerability targeting means that reactive security postures are no longer sufficient. Security programs must transition toward a model of continuous exposure management, ensuring the perimeter is consistently audited for the exposed assets that groups like Storm-1175 look for.

While prompt injection risks in tools like Grafana represent emerging methods for data access, the most immediate risk remains the rapid targeting of the network edge. The connection between these two areas is the credential. Whether an unauthorized party uses an N-day vulnerability or a prompt injection technique, the objective is often the privilege escalation required for broad environment control. Security teams that focus on hardening the identity layer while simultaneously narrowing their patching windows will be best positioned to protect their organizations against this cycle of high-velocity threats.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Grafana resolves indirect prompt injection vulnerability in AI assistant</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/bab7fca2-eebd-43d5-85d0-a00e4c1beae0</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/bab7fca2-eebd-43d5-85d0-a00e4c1beae0</guid>
        <pubDate>Wed, 08 Apr 2026 03:07:01 GMT</pubDate>
        <description>Security researchers identified a prompt injection vulnerability in Grafana&apos;s AI components that could have allowed unauthorized parties to exfiltrate sensitive data. Grafana quickly patched the underlying issue in its Markdown renderer, demonstrating the value of coordinated disclosure in securing AI integrations.</description>
        <content:encoded><![CDATA[
            Observability platform Grafana recently resolved a vulnerability that could have allowed unauthorized parties to manipulate its AI capabilities into exposing sensitive data.

Grafana serves as a central hub for compiling and tracking business data, including telemetry, infrastructure health, and financial metrics. Because the platform connects to highly sensitive organizational information, securing its components is a priority for defending business environments.

Security researchers at AI security vendor Noma recently published findings on "GrafanaGhost," an indirect prompt injection vulnerability that could enable a threat actor to exfiltrate data. Noma followed responsible disclosure protocols, and Grafana rapidly patched the core technical issue to protect its users.

## Mechanics of the indirect prompt injection

The vulnerability stems from how Grafana's AI components process external information. To evaluate the AI's security boundaries, Noma researchers looked for user-facing areas where indirect prompts are processed. They identified image tags as a viable path for unauthorized instructions.

While Grafana employs protections to prevent external image rendering from untrusted domains, researchers bypassed these safeguards using protocol-relative URLs (which circumvented domain validation) and the keyword "INTENT" (which instructed the AI model to bypass its standard guardrails). By hiding these instructions on a controlled web page, the researchers demonstrated that the AI could ingest the prompt as benign, inadvertently sending requested sensitive data back to an external server as soon as the image began to load.

Sasi Levi, security research lead at Noma Security, noted that this technique does not necessarily require an affected user to click a malicious link.

"[The threat actor needs] to get their indirect prompt stored in a location that Grafana's AI components will later retrieve and process," Levi told Dark Reading. "Once that [injected prompt] is sitting in the data store, it waits and fires automatically when any user performs a normal interaction with their Grafana instance (like browsing entry logs). The user is the unwitting trigger, not the target of a phishing attempt."

## Vendor response and remediation

Grafana Labs chief information security officer Joe McManus confirmed that Noma's research identified an issue with Grafana's image renderer in its Markdown component, which the company quickly patched.

However, Grafana and Noma differ on the exact interaction requirements for the vulnerability. McManus stated that the technique was not "zero-click" and could not operate autonomously in the background.

"Any successful execution of this [technique] would have required significant user interaction — specifically, the end user would have to repeatedly instruct our AI assistant to follow malicious instructions contained in logs, even after the AI assistant made the user aware of the malicious instructions," McManus said. He also noted there is no evidence of this bug being used in the wild, and no data was exposed from Grafana Cloud.

In response, Levi maintained that the sequence requires fewer than two steps and that the AI processed the indirect prompt autonomously, interpreting the log content as legitimate context without generating a warning or asking the user to confirm.

Despite the differing perspectives on the execution mechanics, both teams emphasized their shared commitment to user protection. The vulnerability is documented and fully patched, ensuring that Grafana users remain secure against this specific prompt injection technique.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Storm-1175 methodology accelerates Medusa ransomware deployment via recently disclosed vulnerabilities</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/7a04b119-ed27-4fe7-8a72-830b171f72f1</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/7a04b119-ed27-4fe7-8a72-830b171f72f1</guid>
        <pubDate>Wed, 08 Apr 2026 03:07:01 GMT</pubDate>
        <description>Threat group Storm-1175 is operationalizing newly disclosed vulnerabilities to deploy Medusa ransomware, often within days of public disclosure. Security teams can protect their environments by prioritizing rapid patch management, securing privileged credentials, and hardening endpoint defenses against tampering.</description>
        <content:encoded><![CDATA[
            The financially motivated threat group tracked as Storm-1175 is operating at an accelerated pace to deliver Medusa ransomware, compressing the timeline between vulnerability disclosure and initial access.

Recent analysis from Microsoft Threat Intelligence, reported by Dark Reading's Rob Wright, details how Storm-1175 conducts high-velocity campaigns that target known vulnerabilities. The group specifically focuses on the operational window between a vulnerability's initial public disclosure and the widespread deployment of security patches. Microsoft researchers have also observed the group utilizing several zero-day vulnerabilities prior to public awareness.

Storm-1175's methodology relies heavily on speed, prioritizing rapid progression from initial access to data exfiltration and the introduction of Medusa ransomware. According to Microsoft, this sequence is completed "often within a few days and, in some cases, within 24 hours."

"The threat actor's high operational tempo and proficiency in identifying exposed perimeter assets have proven successful, with recent intrusions heavily impacting healthcare organizations, as well as those in the education, professional services, and finance sectors in Australia, United Kingdom, and United States," Microsoft noted in its technical analysis.

This accelerated timeline highlights the necessity for security teams to reduce their mean time to patch for critical flaws. Sherrod DeGrippo, general manager of threat intelligence at Microsoft, observed that given the group's operational speed, "patches should be prioritized immediately upon release."

## Vulnerability utilization and rapid timelines

Microsoft researchers identified that Storm-1175 has rapidly leveraged more than a dozen known vulnerabilities (N-days). The most recent example is CVE-2026-1731, a critical remote code execution vulnerability affecting BeyondTrust Remote Support and older versions of Privileged Remote Access (PRA). Following its initial disclosure on February 6, the flaw was quickly targeted in the wild, prompting the Cybersecurity and Infrastructure Security Agency (CISA) to add it to the Known Exploited Vulnerabilities (KEV) catalog one week later.

Other notable vulnerabilities targeted by Storm-1175 include:
* CVE-2025-31161: A critical authentication bypass vulnerability in CrushFTP's file transfer software.

* CVE-2024-27198: A critical authentication bypass flaw affecting JetBrains' TeamCity, which saw widespread scanning and targeting days after its March 2024 disclosure.

* CVE-2023-21529: A Microsoft Exchange vulnerability disclosed in February 2023, marking the first confirmation of its use by this specific group.

In addition to N-days, Microsoft connected several zero-day vulnerabilities to Storm-1175 operations. A recent instance involves CVE-2026-23760, a critical authentication bypass in SmarterMail that was also utilized by other threat groups, including the China-linked Storm-2603. Furthermore, Storm-1175 operationalized CVE-2025-10035, a maximum-severity flaw in the License Servlet of GoAnywhere Managed File Transfer (MFT). Microsoft's telemetry indicates both zero-days were leveraged approximately one week prior to their respective public disclosures.

"While these more recent attacks demonstrate an evolved development capability or new access to resources like exploit brokers for Storm-1175, it is worth noting that GoAnywhere MFT has previously been targeted by ransomware attackers, and that the SmarterMail vulnerability was reportedly similar to a previously disclosed flaw," Microsoft stated. "These factors may have helped to allow subsequent zero-day exploitation activity by Storm-1175, who still primarily leverages N-day vulnerabilities."

## Post-access movement and security tampering

Following initial access, Storm-1175 relies on a specific set of tools to navigate affected environments. The group frequently uses legitimate remote monitoring and management (RMM) software to support lateral movement, the Impacket framework for credential dumping, and the command-line utility Rclone to exfiltrate data.

A notable component of the group's methodology is its capability to interfere with security solutions, specifically Microsoft Defender Antivirus. Threat actors modified program settings stored within the Windows registry, creating conditions that allowed Medusa ransomware components to execute without interruption.

Implementing these registry modifications requires the unauthorized party to first secure highly privileged account access, making the credential dumping phase of the sequence a critical intervention point for defenders.

"For this reason, prioritizing alerts related to credential theft activity, which typically indicate an active attacker in the environment, is essential to responding to ransomware signals and preventing attackers from gaining privileged account access," Microsoft noted.

## Defensive recommendations

To protect environments against these rapid operational timelines and tampering techniques, security teams can implement several practical hardening measures.

To prevent security software interference, organizations should enable Windows Defender Antivirus tamper protection features across their tenants. Additionally, security administrators can apply the `DisableLocalAdminMerge` setting, which prevents unauthorized users including leveraging local administrator privileges and establish antivirus exclusions.

For infrastructure protection, organizations are advised to isolate web-facing systems from the broader internet where possible. Any servers requiring public accessibility should be placed behind a Web Application Firewall (WAF), a proxy server, or within a properly segmented DMZ. Finally, enabling Windows Credential Guard will help protect credentials stored in process memory, directly mitigating the credential dumping techniques that allow the later stages of this methodology.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Navigating Converging Supply Chain Risks: Mitigation Strategies for prt-scan, Axios, and Fortinet Vulnerabilities</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/a2ced591-0bcb-4935-85e5-e2e3687efd6b</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/a2ced591-0bcb-4935-85e5-e2e3687efd6b</guid>
        <pubDate>Tue, 07 Apr 2026 03:17:07 GMT</pubDate>
        <description>Recent supply chain compromises demonstrate a shift toward both industrialized automation and highly targeted social engineering against open-source maintainers. This assessment details the mechanics of the prt-scan campaign, the UNC1069 Axios incident, and critical vulnerabilities in Fortinet and Next.js, providing actionable guidance to harden development environments and detect unauthorized activity.</description>
        <content:encoded><![CDATA[
            Software supply chains currently face diverging targeting methodologies. Defensive teams are managing a situation where high-volume, AI-assisted automation tests CI/CD pipelines for misconfigurations, while state-sponsored actors concurrently use patient, long-term social engineering to compromise trusted code libraries. Recent details regarding the "prt-scan" campaign on GitHub and the compromise of the Axios NPM package show a clear shift in the baseline for supply chain security.

The threat environment shows a professionalization of these operations, moving away including sporadic manual efforts toward industrialized systems. The "prt-scan" campaign utilized AI-assisted automation and initiate over 500 unauthorized access attempts against GitHub repositories. Though the success rate was below 10%, the scale of the effort. Unfolding across six waves using six different accounts—allowed a single actor to impact dozens of environments and introduce unauthorized code into at least two NPM packages. This campaign focused specifically on the `pull_request_target` trigger in GitHub Actions. This feature can inadvertently allow workflows to run with elevated permissions when triggered by untrusted forks if not strictly configured.

In a different approach from automated campaigns, the North Korean group UNC1069 employed a systematic social engineering strategy to compromise the lead maintainer of Axios, a library downloaded over 100 million times weekly. This high-fidelity operation prioritized patience over volume. The actors spent weeks building rapport, eventually inviting the maintainer to a convincing Slack workspace and a spoofed Microsoft Teams meeting. During the call, they prompted the installation of a "technical update," which deployed a remote access Trojan (RAT). This compromise provided full control over the developer’s workstation, bypassing two-factor authentication (2FA) by capturing the post-authentication state. Consequently, the actors were able to publish unauthorized versions of Axios directly to the NPM registry.

Alongside these supply chain risks, a critical zero-day vulnerability in Fortinet’s infrastructure requires immediate attention. Fortinet issued an emergency patch for CVE-2026-35616, a critical pre-authentication API access bypass in FortiClient Endpoint Management Server (EMS). With a CVSS score of 9.1, this vulnerability allows an unauthenticated party to execute arbitrary code or commands. The Cybersecurity and Infrastructure Security Agency (CISA) added this to its Known Exploited Vulnerabilities catalog, setting an April 9 remediation deadline for federal agencies. Security researchers have noted public proof-of-concept code on GitHub. While unauthorized activity appears limited to a single source at present, the availability of public access methods indicates a high probability of broader targeting.

Compounding current security priorities is the UAT-10608 campaign, a large-scale automated credential harvesting operation targeting public-facing Next.js applications. This campaign leverages the React2Shell vulnerability (CVE-2025-55182), a pre-authentication remote code execution flaw in React Server Components. Unauthorized actors are using automated scanners, likely utilizing services like Shodan—to locate vulnerable endpoints and deploy the NEXUS Listener framework. Acting as a command-and-control platform with a built-in search interface, this framework allows operators to systematically index and exfiltrate environment secrets, SSH keys, and cloud tokens from compromised hosts globally.

## Detection and Remediation Opportunities

For defenders, understanding the technical mechanics of these campaigns provides clear detection opportunities. To identify Next.js targeting, security teams should monitor web application hosts for unexpected processes originating from the `/tmp/` directory, particularly those with randomized, dot-prefixed names. Unusual `nohup` invocations that disconnect from standard application workflows also strongly indicate NEXUS Listener activity. On the network side, defenders should investigate any outbound HTTP/S connections from application containers that do not align with verified production endpoints. For organizations managing Fortinet environments, applying the emergency hotfix for versions 7.4.5 and 7.4.6 is the highest priority, as version 7.4.7 is pending its standard release.

Hardening the development environment requires a move toward stricter CI/CD governance. The prt-scan activity demonstrates the value of requiring manual approval for all outside collaborators before allowing any GitHub Action workflows to execute. Additionally, teams should configure the default state for the `GITHUB_TOKEN` to read-only.

The Axios incident offers a challenging lesson: traditional identity protections like 2FA may not protect a targeted developer’s workstation. Organizations can improve their resilience by isolating development environments from everyday communication tools and implementing continuous monitoring for unauthorized package publications. If an organization finds it has used the affected Axios versions (1.14.1 or 0.30.4), simply updating the library is insufficient. All secrets and credentials present on the affected developer’s machine or within the CI/CD runners must be rotated immediately to secure the environment.

These developments signal a lasting shift in how software ecosystems are targeted. Automation has lowered the barrier to entry for wide-scale operations, while sophisticated social engineering continues to advance. The long-term methodology seen in the Axios incident indicates that maintainers of high-impact open-source projects are now primary intelligence targets, similar to historically targeted executive roles. We anticipate more campaigns blending these approaches, utilizing automation for target identification and refined social engineering to gain access.

Currently, it remains unclear whether the prt-scan actor was experimental or preparing more refined automation scripts. Furthermore, while Fortinet has addressed the immediate API bypass, threat actors frequently target management infrastructure using secondary access methods after the initial patch cycle. Security teams should maintain vigilance for anomalous activity even after applying the latest fixes. Triage researchers continue to work alongside our partners to ensure these detection and remediation strategies are effectively integrated into their defenses.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Automated Credential Harvesting Campaign Targets React2Shell Vulnerability</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/92f56515-8e5f-4e35-acd7-2a17e93b4518</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/92f56515-8e5f-4e35-acd7-2a17e93b4518</guid>
        <pubDate>Tue, 07 Apr 2026 03:17:06 GMT</pubDate>
        <description>A widespread credential harvesting campaign tracked as UAT-10608 is targeting the React2Shell vulnerability (CVE-2025-55182) in public-facing Next.js applications. Threat actors are deploying an automated framework to extract sensitive system data, requiring organizations to apply patches, rotate credentials, and monitor for specific access artifacts.</description>
        <content:encoded><![CDATA[
            A widespread credential harvesting campaign is targeting public-facing web applications vulnerable to React2Shell, deploying an automated collection framework to extract credentials and system data. Cisco Talos researchers identified the activity, attributing it to a threat cluster tracked as UAT-10608.

The campaign has resulted in the compromise of at least 766 hosts across multiple geographic regions and cloud providers, according to a recent Talos report.

Threat actors target Next.js applications vulnerable to CVE-2025-55182, a pre-authentication remote code execution (RCE) flaw widely known as React2Shell—to gain initial access to affected networks. React2Shell affects React Server Components (RSCs). If targeted, affected endpoints may deserialize inbound HTTP requests without adequate validation or sanitization.

Following initial access, unauthorized parties deploy a framework dubbed NEXUS Listener to systematically collect credentials, SSH keys, cloud tokens, and environment secrets. The framework includes a graphical user interface (GUI) with search capabilities, allowing actors to index and review the exfiltrated data.

## Automated identification and extraction sequence

The threat cluster utilizes automated scanning methods. Likely analyzing host profile data including services such as Shodan or Censys—to identify publicly accessible Next.js deployments and probe them for RSC configuration vulnerabilities.

The unauthorized access sequence begins by identifying a web application running a vulnerable version of RSCs or a framework built on top of it. The threat actor crafts a malicious serialized input and sends it directly and a Server Function endpoint via an HTTP request, requiring no authentication. The server deserializes the input, leading to arbitrary code execution within the server-side Node.js process.

## The NEXUS Listener framework

Once a vulnerable endpoint is identified, the NEXUS Listener framework operates without manual interaction. It functions as both a command-and-control (C2) platform and an analytics dashboard, organizing extracted data into a searchable dataset.

This detailed mapping of affected infrastructure, including services, cloud usage, and third-party integrations—elevates the risk of subsequent unauthorized access, social engineering efforts, or the sale of network access to other malicious actors.

## Defense and remediation recommendations

Protecting systems from the UAT-10608 campaign requires a methodical approach. The primary remediation step is patching CVE-2025-55182 across all Next.js deployments, which remains a critical priority for exposed environments.

Security teams should also proactively rotate all potentially exposed credentials and API keys. Enforcing least-privilege access, restricting access to cloud metadata services, and avoiding SSH key reuse will limit lateral movement if a system is compromised. Implementing regular secrets scanning provides an additional layer of visibility to prevent credential exposure.

To identify potential UAT-10608 activity, defenders can monitor web application hosts for specific artifacts. Cisco Talos recommends investigating the following indicators:
* Unexpected processes originating from `/tmp/` with randomized dot-prefixed names.

* `nohup` invocations in process listings that are disconnected from known application workflows.

* Unusual outbound HTTP/S connections from application containers to non-production endpoints.

* Evidence of `__NEXT_DATA__` exposing server-side secrets in rendered HTML.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Fortinet releases emergency patch for critical FortiClient EMS vulnerability</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/06e73b71-2b85-40b7-856b-134e37a41456</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/06e73b71-2b85-40b7-856b-134e37a41456</guid>
        <pubDate>Tue, 07 Apr 2026 03:17:06 GMT</pubDate>
        <description>Fortinet has issued a critical hotfix for CVE-2026-35616, a pre-authentication API access bypass in FortiClient EMS that has been targeted in the wild. Organizations should apply the hotfix or upgrade to version 7.4.7 immediately to protect their systems from unauthorized access.</description>
        <content:encoded><![CDATA[
            Fortinet has deployed an emergency patch to address CVE-2026-35616, a critical zero-day vulnerability in its FortiClient Endpoint Management Server (EMS) software that threat actors have actively targeted in the wild.

Disclosed on Saturday, the vulnerability is categorized as an improper access control issue and carries a CVSS score of 9.1. Left unpatched, it enables an unauthenticated unauthorized party to execute code or commands through crafted requests.

In a security advisory, Fortinet confirmed that unauthorized activity has occurred and advised customers to install the hotfix for FortiClient EMS versions 7.4.5 and 7.4.6 immediately. Fortinet noted that the upcoming FortiClient EMS 7.4.7 release will include the standard fix, but the hotfix fully prevents unauthorized access in the interim.

Security researcher Nguyen Duc Anh and Simo Kohonen, founder and CEO of Defused, discovered and reported the vulnerability. At this stage, unauthorized activity appears limited to a single source.

This vulnerability follows another recent FortiClient EMS security flaw, CVE-2026-21643. Defused researchers identified unauthorized access attempts against that critical SQL injection vulnerability late last month after its disclosure and patch on February 6. Kohonen reported no visible overlap in threat activity between the two vulnerabilities, noting that activity for the newer zero-day remains isolated to the original access method.

## Technical details and discovery

Defused categorized CVE-2026-35616 as a "pre-authentication API access bypass" that allows an unauthorized party to entirely circumvent API authorization. The security firm identified the vulnerability using its Radar feature, a large-scale anomaly detector designed to surface new vulnerabilities and trends from honeypot data. Radar previously identified targeting activity for CVE-2026-3055, a critical vulnerability in Citrix NetScaler ADC and NetScaler Gateway.

On Monday, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-35616 to its Known Exploited Vulnerabilities (KEV) catalog. Federal civilian executive branch (FCEB) agencies have until April 9 to remediate the vulnerability.

Also on Monday, Tenable senior staff engineer Scott Caveza noted the presence of a public proof-of-concept on GitHub. While Tenable researchers have not yet verified the code, Caveza advised that unauthorized activity will likely increase as access methods become public.

## Historical targeting of Fortinet environments

Threat actors consistently target Fortinet infrastructure, requiring organizations to maintain strict patching cadences.

In January, threat actors targeted a critical zero-day vulnerability to gain access to customer systems through the FortiCloud single sign-on (SSO) feature. During the same month, threat actors widely targeted CVE-2025-64155, a critical command-injection vulnerability in FortiSIEM.

In early December, Fortinet disclosed two critical authentication bypass vulnerabilities affecting FortiOS, FortiWeb, FortiProxy, and FortiSwitchManager. One of these, CVE-2025-59718, was added to CISA's KEV catalog shortly after. In November, unauthorized parties targeted CVE-2025-64446, a critical path traversal vulnerability in FortiWeb.

Threat actors also focus on existing misconfigurations. In February, Amazon Web Services researchers found that a threat actor had gained unauthorized access to hundreds of FortiGate devices by using AI to identify weak credentials, exposed ports, and related security gaps.

*(Note: The original article detailing these events was authored by Rob Wright, Senior News Director at Dark Reading.)*
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Axios NPM incident demonstrates systemic social engineering targeting open-source maintainers</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/89037053-dc90-4701-be5e-8900dd8dc6f5</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/89037053-dc90-4701-be5e-8900dd8dc6f5</guid>
        <pubDate>Tue, 07 Apr 2026 03:17:06 GMT</pubDate>
        <description>Late last month, the popular Axios NPM package was compromised following a systematic social engineering campaign targeting its lead maintainer. This incident indicates a shift in threat actor methodology toward high-trust open-source developers and requires a renewed focus on continuous monitoring and account protections.</description>
        <content:encoded><![CDATA[
            Late last month, the NPM package for Axios—a widely used JavaScript HTTP client library downloaded over 100 million times per week—experienced a security incident. A threat actor, identified by researchers as the North Korean state-sponsored group UNC1069, compromised the account of lead maintainer Jason Saayman. This unauthorized access was used to publish two compromised versions (1.14.1 and 0.30.4) containing a malicious dependency, `plain-crypto-js`, which installed a remote access Trojan (RAT).

The software development community rapidly identified the unauthorized code, and the affected versions were removed from the NPM registry within a few hours.

In a post-mortem published on GitHub, Saayman detailed the sequence of events. The compromise originated from a systematic social engineering campaign that began two weeks prior. Threat actors posed as the founder of a legitimate company, inviting the maintainer to a highly convincing Slack workspace with multiple active channels. From there, the actors scheduled a meeting on Microsoft Teams. Upon joining the spoofed meeting environment, Saayman was prompted to install an update to resolve an apparent technical issue. This file contained the RAT.

The installed RAT provided the threat actors with full, unilateral control over the maintainer's workstation. Security researcher Taylor Monahan noted in the technical analysis that because the RAT captures the post-authentication state of the device, it renders two-factor authentication (2FA) ineffective for preventing the subsequent unauthorized package publication.

This campaign extends beyond a single library. Monahan’s analysis indicates that these specific North Korean threat actors have historically targeted cryptocurrency founders and venture capital executives using similar methods to establish long-term access or deploy credential stealers.

Development security vendor Socket recently published research showing this systematic approach is now targeting the broader open-source software community. Numerous developers and executives, including Socket CEO Feross Aboukhadijeh, reported experiencing the same slow-burn social engineering tactics. The methodology relies on patience—scheduling and rescheduling calls without urgency to disarm the target before deploying the unauthorized executable.

Sarah Kern, principal threat researcher at Sophos, attributes this level of operational maturity to state-sponsored backing. The objective is to secure write access to packages with massive distribution scales. As Aboukhadijeh noted, compromising an open-source maintainer provides a scale of impact that traditional social engineering methods rarely achieve, extending risk to every organization running the affected code.

Several factors contribute to this shift. The ability to generate convincing personas and maintain coherent, long-term conversations has reduced the cost of building trust. Additionally, delivery mechanisms like ClickFix have streamlined the execution phase, while the underlying operational infrastructure has matured significantly, according to Tom Hegel, distinguished threat researcher at SentinelOne. Hegel advises the security community to treat this as a permanent shift in the threat environment.

To protect development environments, organizations using Axios should verify their lockfiles for `axios@1.14.1`, `axios@0.30.4`, or the `plain-crypto-js` dependency. If found, teams should downgrade to a known safe version (such as 1.14.0), remove the affected dependency, and immediately rotate all secrets and credentials present on the affected machine or CI/CD runner.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>AI-Assisted Supply Chain Activity Targets GitHub Actions Workflows</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/aa405c3b-d745-40dc-8b8c-9007667b80b1</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/aa405c3b-d745-40dc-8b8c-9007667b80b1</guid>
        <pubDate>Tue, 07 Apr 2026 03:17:05 GMT</pubDate>
        <description>An analysis of the automated &quot;prt-scan&quot; campaign targeting GitHub&apos;s pull_request_target trigger. This review covers the timeline, the methodologies used by the threat actor, and actionable steps organizations can take to harden their CI/CD pipelines against unauthorized access.</description>
        <content:encoded><![CDATA[
            A threat actor recently leveraged AI-assisted automation to initiate hundreds of unauthorized access attempts against open-source software repositories on GitHub.

Cloud security vendor Wiz analyzed more than 450 of these attempts, finding that fewer than 10% successfully executed. However, the threat actor did manage to introduce unauthorized modifications to at least two NPM packages. Charlie Eriksen, a researcher at Aikido Security, first observed the activity on April 2, 2026. A subsequent investigation by Wiz revealed the campaign actually began three weeks earlier on March 11, unfolding across six waves and utilizing six different GitHub accounts tied to a single threat actor.

## Secondary AI-augmented supply chain campaign

Tracked by Wiz as "prt-scan," this activity represents the second recent instance where a threat actor applied AI-assisted automation to target repositories configured with the `pull_request_target` workflow trigger on GitHub. It follows a late-February campaign known as “hackerbot-claw,” which manipulated the same feature in an attempt to access GitHub tokens, secrets, environment variables, and cloud credentials.

While the hackerbot-claw activity was relatively brief and focused on high-profile repositories, prt-scan operated on a much broader scale. The threat actor opened well over 500 pull requests across both small and large GitHub projects, though with a lower overall success rate.

Wiz researchers noted in a recently published report that the successful incidents primarily affected small hobbyist projects, typically exposing only ephemeral GitHub credentials tied to the specific workflow. With minor exceptions, the campaign did not yield access to production infrastructure, cloud credentials, or persistent API keys.

The broader takeaway for security teams is the evolving role of AI-augmented automation in software supply chain security. Automation enables lower-sophistication threat actors to initiate large-scale activity across hundreds of targets with significantly less time and effort than previously required.

To understand the mechanism, it helps to look at how continuous integration environments process code. Developers use pull requests to propose project changes so maintainers can review and merge them. In GitHub Actions, the `pull_request_target` trigger automatically runs workflows in the context of the main repository whenever a pull request is submitted—even if that request originates from an untrusted fork. Because this action runs with full repository permissions and can access secrets, an unauthorized pull request can expose API keys or credentials. Wiz noted that this trigger is a well-documented misconfiguration when applied to untrusted pull requests without additional restrictions.

## Methodologies and execution flaws

In the prt-scan campaign, the threat actor's methodology began by scanning for repositories utilizing the `pull_request_target` trigger. They then forked those repositories, created a branch, and embedded unauthorized code within a seemingly routine configuration update. The goal was to prompt the project into executing the code automatically, allowing the actor to access sensitive data.

Wiz’s analysis identified a testing phase beginning March 11, during which the threat actor opened 10 pull requests containing unauthorized code. This initial phase continued through March 16. Following a nearly two-week pause, the actor resumed activity at a significantly higher velocity, indicating the use of AI-enabled automation. Over a 26-hour period starting April 2, the actor opened approximately 475 pull requests containing complex, language-aware execution scripts intended to access credentials.

Despite the ambitious design of these scripts, the actual implementation was flawed and indicated a misunderstanding of GitHub’s permission model. According to Wiz, the threat actor built a multi-phase script but populated it with techniques that contradict established GitHub security boundaries and would rarely function in practice. For instance, attempts to automatically apply labels to bypass workflow gates failed because the actor lacked the necessary write permissions in the target repositories.

Even with this flawed approach, the sheer volume of attempts meant that a 10% success rate still resulted in dozens of exposed environments. To safeguard against similar automated activity, organizations should harden their GitHub environments. Security teams can protect their repositories by requiring approval for all outside collaborators before workflows execute, assigning read-only permissions to the `GITHUB_TOKEN` by default, and avoiding the use of the `pull_request_target` trigger for untrusted code submissions.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Navigating Recent Supply Chain Incidents and Mobile OS Patching Shifts</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/3f5ea2a1-9e89-479b-babc-59e1ea30952b</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/3f5ea2a1-9e89-479b-babc-59e1ea30952b</guid>
        <pubDate>Sat, 04 Apr 2026 03:13:29 GMT</pubDate>
        <description>Recent security incidents involving modified open-source development tools and new mobile OS vulnerabilities require immediate attention from security teams. This briefing details the technical findings and provides actionable remediation steps to protect CI/CD pipelines and enterprise mobile fleets.</description>
        <content:encoded><![CDATA[
            The security community is currently navigating a dense cluster of software supply chain incidents and a rare shift in mobile OS patching strategy, both of which show how rapidly the window for defensive response is closing. For security teams, the most immediate development is Apple’s decision to backport critical patches for the DarkSword vulnerability sequence to iOS 18. This move, finalized on April 1, is designed to protect organizations that utilize "n-minus-one" patching policies. Strategies that typically favor stability by staying one major version behind the current release. While Apple usually limits security updates for older operating systems to hardware that cannot support the newest software, the public leak of DarkSword’s methodology on GitHub on March 22 forced a change in posture. The availability of these tools to unauthorized parties means that remaining on a previous OS version introduces elevated risk for enterprise fleets.

The broader situation today is dominated by the expanding fallout from TeamPCP’s supply chain campaign. Within the last 48 hours, both the AI startup Mercor and the European Commission (EC) have disclosed significant security incidents tied to modified open-source tools. These events demonstrate a highly compressed intrusion timeline; in the case of the EC, threat actors obtained an AWS API key on March 19, the exact same day TeamPCP began distributing a modified version of the Trivy code-scanning tool. This indicates that the response window for supply chain incidents has shrunk from days to hours. Furthermore, the situation has been complicated by a convergence of threat actors. While TeamPCP initiated the intrusions, secondary groups like ShinyHunters and Lapsus$ are now claiming to possess massive datasets—91 GB from the EC and 4 TB from Mercor, suggesting that once initial access occurs, multiple threat groups may move in simultaneously to monetize the exposure.

## Technical capabilities of mobile and cloud threats

Technically, the DarkSword and Coruna frameworks represent a significant escalation in mobile surveillance capabilities. Coruna is a sophisticated, multi-sequence framework comprising 23 vulnerabilities that allows threat actors to establish command-and-control over SMS. This effectively turns an iPhone into a self-propagating platform for harvesting contacts and distributing unsafe links. DarkSword presents unique detection challenges. Unlike Coruna, it does not root the device. Instead, it inherits the privileges of legitimate processes and escalates just enough to access processors with Ring 0 access. This stealthy approach (T1068) makes it nearly invisible to traditional root detection mechanisms. Defenders should be aware that while Apple’s updates mitigate these specific risks, the market for "n-day" iOS frameworks is expanding, and criminal campaigns have already been observed spoofing organizations like the Atlantic Council to deliver these unauthorized components.

In the cloud and development space, the methodology used by TeamPCP reveals a systemic weakness in CI/CD pipelines (T1195.002). After gaining initial access through modified packages like Trivy or the Axios JavaScript library, actors consistently use the TruffleHog tool to hunt for unsecured credentials (T1552) within AWS, Azure, and SaaS environments. This has led to the extraction of sensitive data including S3 buckets and container instances. The risk is being amplified by the rapid integration of generative AI into development workflows. Data from the 2026 Open Source Security and Risk Analysis (OSSRA) report shows that AI-driven development has contributed and a 74% year-over-year increase in codebase size, while the mean number of vulnerabilities per codebase has surged by 107%. Many of these findings trace back to "zombie components"—outdated libraries that have seen no development activity for years but remain embedded in critical infrastructure.

The recent accidental publication of a source map for Anthropic’s Claude Code tool further illustrates the fragility of the modern developer workstation. By exposing over half a million lines of TypeScript, the leak provided a roadmap for researchers and threat actors to understand the internal context pipelines and sandbox boundaries of AI coding agents. For defenders, the primary concern is that a compromised AI agent, which maintains persistent access to the shell and network, could allow an unauthorized instruction to survive "context compaction" and eventually flow into production code. This introduces a new class of persistence that bypasses standard output guardrails.

## Remediation and continuous authentication

For security teams, the priority is an immediate audit of CI/CD runners and the rotation of all cloud credentials that may have been exposed to affected tools like Trivy, KICS, or LiteLLM. Simply removing a modified package is insufficient; if an API key was harvested, the unauthorized party likely already has a foothold in adjacent environments. Organizations should also reassess their "n-minus-one" policies for mobile devices. While these policies are intended to ensure uptime, the DarkSword incident proves that threat actors can leverage the gap between OS releases faster than many IT departments can react. Monitoring for anomalous activity in cloud environments, specifically unauthorized use of TruffleHog or unusual S3 bucket access—is essential.

Looking forward, the shift toward continuous biometric authentication may offer a way to secure these high-trust environments. Researchers at Rutgers University have developed "VitalID," a software-based approach for XR headsets that uses motion sensors to analyze skull vibration harmonics generated by a user’s heartbeat and breathing. This provides a passive, continuous authentication signal that ensures the authorized user is still the one wearing the device, preventing session hijacking in spatial computing environments. While still in the research and SDK phase, such technologies represent a necessary move away from initial access checks toward a model of constant verification.

At this stage, several aspects of the TeamPCP campaign remain uncertain, including the true extent of the data removed including Mercor and whether the overlap between TeamPCP and extortion groups like Lapsus$ represents a formal partnership or parallel competitive activity. Security teams should operate under the assumption that any secret exposed and a compromised development tool is fully compromised and prioritize total credential re-issuance.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Recent supply chain incidents reveal systemic risks in CI/CD and AI development pipelines</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/4ae04b45-a246-4c47-a0dd-b28403d1a0c9</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/4ae04b45-a246-4c47-a0dd-b28403d1a0c9</guid>
        <pubDate>Sat, 04 Apr 2026 03:13:28 GMT</pubDate>
        <description>A cluster of software supply chain events involving major open-source projects and AI coding assistants demonstrates the vulnerabilities inherent in modern development environments. By analyzing these incidents alongside recent open-source risk data, security teams can implement structural safeguards to protect continuous integration pipelines and credential-rich developer workstations.</description>
        <content:encoded><![CDATA[
            A sequence of security incidents affecting widely used software projects within a 10-day period points to a growing requirement for systemic oversight in software supply chains. Events involving the Trivy security scanner, the Axios JavaScript package, Checkmarx's KICS static-code analyzer, the LiteLLM Python library, and the accidental publication of Anthropic's Claude Code source map all demonstrate how development pipelines have become primary surfaces for risk.

These incidents stemmed from varying root causes but shared similar outcomes. Unauthorized parties leveraged a misconfigured GitHub Action in Trivy to capture credentials and push unauthorized code. For Axios, the compromise of a lead maintainer's account resulted in unsafe modifications landing in development environments. Checkmarx acknowledged a similar issue affecting its open-source KICS static-analysis tool via GitHub Actions, prompting the company to advise developers to revoke and rotate secrets and to review their deployment pipelines for suspicious indicators.

In the same period, human error led to the accidental publication of a 59.8MB source map for Anthropic's Claude Code npm package. The file exposed over half a million lines of TypeScript source code. Anthropic responded by issuing copyright violation notices to 96 explicit mirrors on GitHub. During this process, an initial network-wide takedown temporarily affected 8,100 legitimate forks of Anthropic’s public repositories, which the company subsequently corrected.

Jun Zhou, full stack engineer at Straiker, an agentic AI security firm, notes that developer environments are particularly sensitive targets. "Developer workstations are credential-rich, high-trust, low-visibility zones, and AI coding agents operating inside them are amplifying the exposure," Zhou says. The analysis of the Anthropic incident showed that while Claude Code utilized more than 25 bash security validators in its runtime, the publication process lacked a basic content check to prevent the source map from reaching a public registry.

Rami McCarthy, a principal security researcher at Wiz, observes that these events represent common ecosystem weaknesses rather than isolated zero-day vulnerabilities. "We've built a global software infrastructure that relies heavily on the volunteer efforts of open source maintainers, which creates an incredibly uneven security surface," McCarthy says. When unauthorized parties target transitive dependencies, the downstream impact requires complex, ecosystem-wide coordination. The Axios package alone has more than 70,000 direct dependencies, giving any unauthorized modification a substantial scope of impact.

The reality of modern development requires treating the supply chain as critical infrastructure. Security teams are encouraged to build guardrails into continuous integration and continuous deployment (CI/CD) environments, assume dependencies are untrusted by default, and implement ecosystem-wide detection for abnormal package behavior.

The widespread adoption of generative AI has accelerated software creation, which in turn introduces new complexities to supply chain management. According to Black Duck’s 2026 Open Source Security and Risk Analysis (OSSRA) report, which analyzed 947 commercial codebases across 17 industries, the integration of AI tools correlates with a 74% year-over-year increase in the mean number of files per codebase, and a 30% increase in open-source components.

The OSSRA data shows that 65% of organizations experienced a software supply chain incident in the past 12 months. Concurrently, the mean number of open-source vulnerabilities per codebase rose by 107% to an average of 581. The audit found that 87% of codebases contained at least one vulnerability, with 78% housing high-risk issues and 44% containing critical-risk findings. Additionally, 68% of codebases contained open-source license conflicts.

Tim Mackey, head of software supply chain risk strategy at Black Duck, cautions that development teams often interpret vulnerability management as simply updating every component to the newest release. However, the data indicates that older versions sometimes offer a more stable balance of patched code and fewer known issues—with the third-most recent version frequently being the most secure on average.

"Immediate patching seems reasonable, but in reality teams need to perform a risk-based analysis of their dev processes," Mackey says, noting that the residual effects of compromised container images can persist over time. The Black Duck report also identified a pervasive "zombie component" issue: 93% of codebases contained components with no development activity in the past two years, 92% contained components four or more years out of date, and only 7% utilized the latest versions.

The public availability of Claude Code's architecture provides a clear view into how AI workflows operate, which moves faster than the security practices designed to monitor them. Jesus Ramon, an AI red team member at Straiker, explains that the exposed code reveals the context pipeline, sandbox boundaries, and permission validators. This visibility allows researchers to understand how cooperative AI models manage data.

Traditional unauthorized packages operate within a bounded runtime. However, an AI coding agent generally maintains access to the file system, shell, network, and Model Context Protocol (MCP) servers. Ramon notes that this introduces a new class of persistence: a manipulated instruction can survive "context compaction"—the process by which the model summarizes and compresses older session data—and re-emerge as a legitimate user directive. From there, it can flow naturally into pull requests and production code without triggering standard output guardrails.

To protect these evolving environments, organizations should focus on restricting access to sensitive CI/CD credentials and implementing rigorous secret-management practices. Security teams can improve resilience by validating dependencies early, limiting session lengths for AI agents to reduce the compaction window, and vetting MCP servers with the same scrutiny applied to standard npm dependencies.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Evaluating skull vibration harmonics for continuous XR authentication</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/e8441b1b-735f-4898-8eb3-2aae512ab181</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/e8441b1b-735f-4898-8eb3-2aae512ab181</guid>
        <pubDate>Sat, 04 Apr 2026 03:13:27 GMT</pubDate>
        <description>Researchers at Rutgers University have developed a methodology for continuous biometric authentication in extended reality (XR) headsets using vital-sign harmonics. This approach offers a passive mechanism to verify user identity and maintain secure session states in enterprise immersive environments.</description>
        <content:encoded><![CDATA[
            Biometric authentication continues to evolve to protect emerging technology environments. A research team led by Rutgers University recently introduced a novel biometric authentication software designed for extended reality (XR) headsets—encompassing virtual and mixed reality hardware. The research focuses on safeguarding digital identities in immersive spaces by analyzing skull vibration harmonics generated by vital signs.

While immersive technology adoption varies in the consumer market, enterprise organizations increasingly rely on XR hardware. Aerospace firms use it for 3D training, and engineers utilize spatial mapping for complex design work. In these environments, protecting sensitive proprietary data and intellectual property requires reliable authentication mechanisms. This research arrives as the security community advocates for stronger access controls, prioritizing passkeys, multifactor authentication (MFA), biometrics, and FIDO security keys to mitigate the risks of credential compromise and prepare for post-quantum cryptographic standards.

## The mechanics of VitalID

The technology, named VitalID, operates entirely as software. It leverages the built-in motion sensors of an XR headset to capture low-frequency mechanical vibrations in the skull produced by a user's breathing and heartbeat.

According to the research summary, these harmonics contain unique biometric signatures specific to a wearer's head and facial structure. The system extracts biometric features including the ratios among these harmonic frequencies. It then applies an adaptive filtering method to reduce motion distortion and uses attention-based deep learning models and maintain continuous user authentication throughout an XR session without requiring active user input. A patent application has been filed for VitalID, and it is positioned for licensing as a software development kit (SDK) or OS-level integration.

## Contextualizing continuous authentication

While VitalID addresses a specific hardware use case, it builds on previous concepts in specialized environments. For example, SkullConduct previously explored user identification via bone conduction in eyewear computing, and the Nymi Band integrates electrocardiogram (ECG) data for authentication in IT and operational technology (OT) spaces.

For most organizational devices outside of XR, established practices remain the baseline. Karolis Arbaciauskas, head of product at NordPass, notes that pairing on-device biometrics with passkeys provides a highly practical path for many organizations. This combination creates a system that is resistant to credential compromise by design, avoids shared secrets, and offers a clear migration path to post-quantum cryptography once platforms standardize it.

However, identity security experts recognize the specific protective value of the Rutgers research for immersive environments. Ralph Rodriguez, president and chief product officer at Daon, points out that the methodology provides a passive, built-in, continuous authentication signal using existing commodity sensors.

Rather than replacing core identity systems—such as account recovery, identity proofing, or strong cryptography—VitalID functions as a continuity and reauthentication mechanism. As enterprise applications, collaboration tools, and health data become accessible through XR headsets, the security requirement shifts including verifying the initial login and ensuring the trusted user remains present over time. Implementing continuous authentication helps maintain a secure session state in environments where a single front-door access check is insufficient.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Scope of TeamPCP supply chain compromises expands alongside overlapping threat activity</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/ef53161c-cb3e-4569-b21a-e6e2648fa9c9</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/ef53161c-cb3e-4569-b21a-e6e2648fa9c9</guid>
        <pubDate>Sat, 04 Apr 2026 03:13:27 GMT</pubDate>
        <description>Following recent compromises involving the LiteLLM and Trivy open-source projects, secondary threat groups are attempting to monetize the exposed data. Organizations must rapidly rotate credentials and audit CI/CD pipelines to mitigate the risk of unauthorized cloud access.</description>
        <content:encoded><![CDATA[
            The impact of TeamPCP's recent supply chain compromises continues to expand across the enterprise field. Following earlier reports of unauthorized code introduced into open-source projects, two affected organizations disclosed related security incidents this week.

On Tuesday, the AI startup Mercor stated on the social media platform X that it was among the companies impacted by a supply chain incident involving LiteLLM. Two days later, the EU's Computer Emergency Response Team (CERT-EU) disclosed that a recent unauthorized access event affecting the European Commission's cloud and web infrastructure stemmed from the previously documented Trivy software supply chain compromise, which is also attributed to TeamPCP. According to CERT-EU, the EC inadvertently installed a modified version of the Trivy code-scanning tool. This installation enabled threat actors to harvest credentials and ultimately access the organization's Amazon Web Services (AWS) environment.

The involvement of third-party extortion groups has complicated the incident response process. CERT-EU confirmed that the cybercriminal group ShinyHunters published an exfiltrated dataset on its leak site, claiming to possess over 91 GB of sensitive EC data, including emails, databases, and confidential documents. Similarly, Lapsus$—a group associated with ShinyHunters and the Scattered Spider collective—claimed to hold 4 TB of Mercor's internal data, including nearly a terabyte of the company's source code. Mercor did not confirm this claim at press time.

It remains unclear exactly how these secondary groups acquired the overlapping data, but security professionals emphasize that organizations must address these converging risks promptly.

## Cloud access methodology and credential harvesting

Disclosures including Mercor and the EC align with technical observations that TeamPCP is actively utilizing stolen credentials to access enterprise cloud infrastructure. Wiz noted that its customer incident response team (CIRT) has observed and responded to multiple incidents where TeamPCP actors used harvested secrets and access victims' AWS, Azure, and software-as-a-service (SaaS) environments.

Wiz researchers detailed how threat actors used the TruffleHog open-source tool to discover and validate exposed credentials within AWS environments. Following initial reconnaissance, the actors accessed resources such as S3 buckets and Amazon Elastic Container Service (ECS) instances to exfiltrate data.

CERT-EU outlined a nearly identical sequence in the European Commission incident. After the modified version of Trivy was deployed, unauthorized actors extracted an AWS API key that provided control over AWS accounts. They subsequently used TruffleHog to locate additional credentials, conducted reconnaissance, and exfiltrated data.

The timeline of these events demonstrates a highly compressed response window. According to CERT-EU, threat actors obtained the EC's API key on March 19—the exact day TeamPCP began distributing modified versions of Trivy. This occurred a day before the Trivy compromise was publicly flagged and several days before Aqua Security, the project’s maintainer, issued a formal disclosure.

Ensar Seker, CISO at SOCRadar, notes that speed of execution is the primary takeaway. "In practice, the response window is now measured in hours, not days," Seker says. "The biggest mistake would be to remove the malicious package but leave the stolen credentials usable, because by then the attackers may already be operating inside adjacent environments."

To effectively mitigate these risks, Seker advises organizations to immediately revoke and rotate exposed secrets, invalidate all tokens, and reissue cloud credentials. Security teams should also review CI/CD runners, inspect GitHub Actions and package publishing workflows, and monitor their cloud and SaaS environments for anomalous activity.

## Convergence of threat actors and evolving risks

The situation is further complicated by the concurrent activities of Lapsus$ and ShinyHunters. According to a post on X associated with TeamPCP, the group appears to be in conflict with ShinyHunters rather than actively collaborating.

"What we are seeing looks less like a clean handoff between separate groups, and more like a convergence of cybercriminal ecosystems around the same access," Seker says. While TeamPCP initiated the supply chain compromises and credential theft, other extortion actors are now attempting to monetize the exposures. "At this stage, that does not prove formal operational alignment, but it does strongly suggest that once high-value access or stolen data emerges from a supply chain intrusion, other extortion actors can move in very quickly to amplify pressure, visibility, and potential profit," Seker notes.

Furthermore, TeamPCP has announced a partnership with Vect, a ransomware group. Tomer Peled, a security researcher at Akamai, observes that this changes the risk profile significantly. Peled notes that the collaboration could provide Vect with access to numerous affected organizations, subjecting them to potential ransomware deployment through TeamPCP's remote access trojan (RAT).

As Akamai documented recently, the modified Telnyx PyPI package contained a three-stage RAT that provides backdoor access to environments running the affected SDK. Given the volume of credentials already obtained by TeamPCP, Peled anticipates the discovery of additional compromised libraries. He assesses that the group will likely use their stolen credentials to continue installing unauthorized access tools across as many systems as possible.

Seker concludes that the involvement of additional threat groups fundamentally alters how organizations must view software supply chain risks. "The old assumption was that a software supply chain attack was mainly a downstream integrity problem," he says. "What these cases show is that it can become an immediate enterprise breach problem, where compromised packages lead to stolen secrets, cloud access, SaaS exposure, repository cloning, and then possible extortion by additional actors."
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Apple backports DarkSword vulnerability patch to iOS 18</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/efb2c2da-8831-40fd-9e17-c65186b98b88</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/efb2c2da-8831-40fd-9e17-c65186b98b88</guid>
        <pubDate>Sat, 04 Apr 2026 03:13:26 GMT</pubDate>
        <description>Apple has extended its security updates for the DarkSword vulnerability chain to iOS 18 devices. This backported patch provides critical protection for organizations relying on n-minus-one patching policies, allowing teams to secure their endpoints without forcing an immediate operating system upgrade.</description>
        <content:encoded><![CDATA[
            After a brief delay, Apple has addressed the vulnerabilities associated with the DarkSword chain for all affected customers, including those who have remained on iOS 18 rather than updating to iOS 26. This release is a significant benefit for organizations managing large device fleets, particularly those enforcing n-minus-one patch management policies that require users to stay one version behind the latest release.

When researchers identify severe vulnerabilities in Apple devices, the company historically provides updates for the latest operating system (OS) and for older devices that lack the hardware to support the new software. For example, when researchers analyzed Coruna, a sophisticated vulnerability framework comprising five distinct sequences across 23 vulnerabilities in iOS versions 13 to 17.2.1—Apple distributed updates to all affected hardware, including older, un-updatable models.

However, users whose devices are capable of upgrading to the newest OS, but who remain on an older version due to corporate mandates or user experience preferences, typically fall outside this support window. For instance, many users have stayed on iOS 18 rather than adopting iOS 26 (which are consecutive major versions in this release cycle). When Apple initially addressed the DarkSword sequence in iOS 26 last year, and subsequently pushed a fix for un-updatable pre-iOS 18 devices on March 24, iOS 18 users faced a difficult choice: execute a full OS upgrade or accept the known security risk.

This posture shifted after the DarkSword methodology was published to GitHub on March 22. With the tooling publicly accessible to unauthorized parties, Apple extended the security update to iOS 18 devices on April 1, providing a necessary safeguard for these remaining users.

Justin Albrecht, principal researcher at Lookout, views the update as a positive shift for user protection. "Apple has taken multiple unprecedented steps on iOS to counter DarkSword and Coruna, to include the backported patches, alert notifications to susceptible devices and published threat guidance on Web-based [incidents]," Albrecht notes. He emphasizes that Apple's serious response should encourage organizations to prioritize applying these updates.

## The technical impact of DarkSword

Initial discussions of DarkSword were somewhat eclipsed by the public disclosure of the Coruna framework earlier the same month.

Coruna is a highly capable tool utilized by advanced threat actors, with evidence suggesting origins as a military contractor project. Rocky Cole, co-founder of iVerify, explains that the framework could establish command-and-control (C2) over SMS. A minor modification could allow it to harvest contacts and distribute messages containing malicious links, effectively creating self-propagating software. Cole identifies this as one of the most severe endpoint risks observed on the platform, prompting Apple's rapid mitigation.

DarkSword was disclosed two weeks after Coruna. While initially viewed as a secondary issue, Cole points out that its methodology is technically stealthier.

"In some ways it's more pernicious, because it didn't root the device," Cole explains. "Coruna rooted. So presumably, if you were doing root detection, you stood a chance of maybe seeing Coruna. But DarkSword doesn't root, it just inherits the privileges of the processes. It gets just enough privilege escalation to access processors that too have Ring 0 access. So in that regard, I think it's actually much harder to detect."

Cole notes that the high adoption rate of iOS 18 compared to iOS 17 (the latest version affected by Coruna), combined with the public availability of the code on GitHub prior to a backported patch, created a significant exposure window that required immediate remediation.

Prior to the leak, operators of surveillance software were already utilizing DarkSword. Following its publication, Lookout's Albrecht observed several active campaigns. "We’ve observed a handful of campaigns being conducted with the malware, to include [an] email phishing campaign conducted by TA446 which spoofed the Atlantic Council. The other campaigns observed appear to be unattributed criminal campaigns which we have been unable to link to a specific group, as well as multiple instances of apparent testing of the malware for unknown purposes."

## Managing ongoing endpoint risk

For enterprise security teams, the timeline of the DarkSword updates highlights ongoing challenges in vulnerability management. Cole notes the gap between the public exposure of the vulnerabilities on GitHub and the availability of a comprehensive patch across operating systems.

He emphasizes that corporate policies force many users to remain on older OS versions, making comprehensive backporting essential for defense. "Let's say you are a business user and your IT department says you have to use what's called an n-minus-one patching cadence, which means you can only use a version that's one version behind, what are you supposed to do in that situation?" Cole asks. "If the patches aren't being backported to all versions, how are you supposed to defend yourself? To me, this just fundamentally challenges the notion that a patching-only strategy is going to be good enough going forward."

Currently, administrators and users who apply the available Apple device updates will mitigate the risks associated with both DarkSword and Coruna. However, the broader trend requires ongoing vigilance. "What I think DarkSword and Coruna together show is that the market for n-day iOS [vulnerability frameworks] is exploding," Cole warns, noting that the cost to acquire these capabilities has fallen rapidly. While these specific sequences are now mitigated, organizations must remain prepared for similar future methodologies.

## About the author

Nate Nelson is a journalist and scriptwriter. He writes for "Darknet Diaries" — a popular podcast in cybersecurity, and co-created the former Top 20 tech podcast "Malicious Life." Before his current work, he was a reporter at Threatpost.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Analyzing Organizational Resilience and Evasive Propagation in Recent Security Incidents</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/b89aa271-71e9-4883-b42b-b85a50b20e7f</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/b89aa271-71e9-4883-b42b-b85a50b20e7f</guid>
        <pubDate>Fri, 03 Apr 2026 03:05:21 GMT</pubDate>
        <description>Recent developments involving Hasbro’s incident response and the Water Saci campaign show the value of proactive business continuity and granular email monitoring. By analyzing these events, security teams can refine endpoint protections and test response strategies to safely maintain operations during network disruptions.</description>
        <content:encoded><![CDATA[
            In the last 24 hours, the security environment has been defined by two contrasting stories: one of successful organizational resilience during an active security incident, and another of a persistent malicious actor using deceptive, self-propagating scripts to bypass traditional email defenses. These developments point to a critical reality for modern security teams: while preventing initial access remains the goal, the ability to maintain operations during remediation and to detect hijacked internal communications separates a manageable incident from a broader operational disruption.

The most significant operational update comes from Hasbro, which recently disclosed an unauthorized network access incident discovered on March 28. In an 8-K filing with the Securities and Exchange Commission, the toy and game manufacturer revealed that it is currently in the midst of remediation efforts that may last several weeks. While the company has been forced to take certain systems offline to isolate the affected areas, their proactive business continuity planning allowed them to continue taking orders and shipping products. This demonstrates the measurable value of having tested response strategies in place before an event occurs.

This incident illustrates the risks facing the retail and manufacturing sectors, which manage high-value environments due to their complex supply chains and sensitive customer data. Analysts note that a multi-week recovery timeline often indicates more intensive recovery efforts, such as those following ransomware, though the company has not officially confirmed the specific nature of the unauthorized access. Regardless of the underlying cause, the ability to navigate a cyber incident without escalating into a full-scale operational crisis is a result of active pressure-testing and simulation, rather than static plans.

Concurrently, a different type of campaign is evolving across Latin America and Spain. A financially motivated group known as Water Saci, or Augmented Marauder, has expanded its reach with a multi-pronged campaign distributing the Casbaneiro banking trojan. This activity relies on self-propagating email scripts that turn affected accounts into distribution hubs. By leveraging trusted sender relationships, the group significantly increases the likelihood that their social engineering attempts will bypass security filters and deceive users.

The technical mechanics of this campaign are designed to evade standard signature-based detection. The sequence typically begins with a phishing email themed around a vague judicial summons. If a user clicks the provided link, they download a password-protected ZIP file containing an unauthorized executable. These ZIP files are often given randomized names for each recipient, creating obstacles for Secure Email Gateways (SEGs) that rely on static indicators. Once the file executes, a script known as Horabot takes control of the affected user's email account. It filters the user's contacts and sends out a new wave of phishing emails, attaching a modified, password-protected version of the initial file.

Once established, the ultimate objective is the deployment of Casbaneiro. This trojan is engineered to activate when a user accesses financial services or cryptocurrency platforms, using screen overlays to capture keystrokes and credentials. It targets a wide array of institutions, including major regional providers like Santander and Banco do Brasil, as well as global platforms like Binance. Despite this sophistication in delivery, researchers note that the malware itself often struggles against modern endpoint protections. In environments with up-to-date security controls, Windows Defender and other EDR solutions frequently identify and block the AutoIT executables used by Water Saci before they can achieve their final objectives.

For defenders, these concurrent developments offer clear priorities. The Hasbro incident shows the necessity of moving beyond prevention-only mindsets. Security teams should prioritize testing their business continuity plans through real-world simulations to ensure that if systems must be taken offline, core revenue-generating operations can persist. This requires close coordination between IT, security, and logistics teams to identify which offline workarounds are actually viable under pressure.

From a detection standpoint, the Water Saci campaign indicates a need for more granular email monitoring. Because the Horabot script uses legitimate, internal, or trusted external accounts to propagate, defenders cannot rely solely on sender reputation. Organizations should consider implementing rules that flag or quarantine password-protected attachments from suspicious sources or those containing uncommon file types like AutoIT scripts. Furthermore, since these campaigns often use randomized filenames, behavioral analysis of the endpoint—monitoring for unauthorized attempts to access contact lists or automate mail sending—is more effective than searching for static hashes.

Looking forward, the persistence of banking trojans in the LATAM region suggests that while these threats are established, they remain profitable enough for malicious actors to continue refining their delivery methods. The shift toward self-propagation via Horabot indicates that unauthorized parties are increasingly aware of the trusted sender blind spot in many security architectures. At the same time, the Hasbro incident provides a blueprint for how large organizations can manage a network disruption without paralyzing their entire business model.

At this stage, the exact entry vector for the Hasbro incident remains undisclosed, and it is unclear if the unauthorized access resulted in any exposure of data. Similarly, while Casbaneiro is often blocked by modern endpoints, its continued use suggests it still finds success in environments with lagging update cycles or fragmented security stacks. We recommend that security teams remain vigilant for judicial-themed phishing and ensure that their endpoint protection rules are specifically tuned to catch the behavioral signatures of credential-harvesting overlays and automated propagation scripts.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Bank Trojan &apos;Casbaneiro&apos; Utilizes Self-Propagating Techniques Across Latin America</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/24ca3b6e-405f-423a-81c9-c218aad3a515</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/24ca3b6e-405f-423a-81c9-c218aad3a515</guid>
        <pubDate>Fri, 03 Apr 2026 03:05:20 GMT</pubDate>
        <description>A financially motivated threat group known as Water Saci is distributing the Casbaneiro banking trojan across Latin America and Spain. By utilizing self-propagating email scripts and social engineering, the campaign aims to capture credentials, though modern endpoint defenses remain highly effective at disrupting this activity.</description>
        <content:encoded><![CDATA[
            Operations originating in Brazil continue to target banking credentials across Spanish-speaking regions using highly self-propagating and evasive delivery mechanisms.

While other regions are often associated with large-scale cryptocurrency incidents or specialized surveillance software, Brazil has developed a prominent ecosystem for banking malware. Threat actors in the region consistently develop financial trojans at a rapid pace, challenging security analysts to track their evolving methodologies.

The cybercrime operation tracked as Water Saci, or Augmented Marauder, has been central to this activity for several years. Recently, the group has divided its resources between two financially motivated campaigns. One campaign operates over [WhatsApp](https://www.darkreading.com/cyberattacks-data-breaches/self-propagating-malware-hits-whatsapp-users-brazil), focuses primarily on Brazil, and has been monitored by researchers since last year.

Security firm BlueVoyant has now identified a [parallel campaign](https://www.bluevoyant.com/blog/augmented-marauders-multi-pronged-casbaneiro-campaigns) operating via email, extending its reach through Latin America and Spain. This latest iteration of Water Saci's methodology features self-propagating capabilities, techniques to bypass email security controls, and mechanisms for financial data theft.

"This threat group seems as if they have a campaign that they try to launch [roughly] every quarter, and they keep changing it, so it's pretty clear whoever this is [is] very active [and] their end goal is to get access to users' bank accounts within the Latin American region," notes Thomas Elkins, SOC security analyst for BlueVoyant. "To me, it's clear that they're going to keep ramping up."

## A self-propagating banking campaign

At first glance, an Augmented Marauder campaign follows familiar social engineering patterns. Recipients receive a standardized email notification referencing a vague, pending judicial summons. Users who interact with the provided link are directed to a landing page that downloads a malicious ZIP file. However, each step in this sequence includes specific mechanisms designed to evade detection or help propagation to new environments.

The file attached to the phishing email is password-protected, which adds a layer of superficial legitimacy and can obscure the contents from [secure email gateways (SEGs)](https://www.techtarget.com/searchsecurity/buyershandbook/What-secure-email-gateways-can-do-for-your-enterprise). Additionally, the ZIP file name is randomized for each recipient, creating an obstacle for signature-based detection tools.

The most notable characteristic is the method used to distribute the judicial summons email. A script deployed later in the execution sequence, a tool identified as Horabot—is engineered to interact with the affected user's email account for self-propagation. It retrieves and filters the user's contacts, then distributes a new wave of [phishing emails](https://www.cybersecuritydive.com/news/phishing-it-leaders-ai-arctic-wolf/802976/) to these potential targets, attaching a modified version of the judicial summons file secured with a newly generated password.

This self-propagating element presents distinct challenges for defenders. Because new targets receive social engineering emails from recognized contacts, they may be more likely to open the attachments. This trusted sender relationship also reduces the likelihood of the emails being quarantined by standard email security solutions.

"And it's pretty smart because it makes it harder to identify where the attack actually originated from," Elkins points out. Between the self-propagating emails and the automated WhatsApp messages in their concurrent Brazilian campaign, "they're finding new ways to automate their attack chains to not just rely on an attacker-based account." This approach complicates the task of identifying infrastructure controlled by the threat actors.

## The limitations of banking trojans

The ultimate objective of this activity is the deployment of Casbaneiro, a traditional banking trojan that activates when affected users access online cryptocurrency or financial service providers. Its [target list](https://www.trendmicro.com/vinfo/us/threat-encyclopedia/malware/trojanspy.win32.casbaneiro.rg) is extensive, encompassing major institutions in Central and South America, such as Santander and Banco do Brasil—as well as payment and cryptocurrency platforms like Binance. Following established patterns, the malware uses screen overlays to simulate legitimate login portals, capturing keystrokes and credential data.

For Elkins, the continued reliance on [Brazilian banking trojans](https://www.darkreading.com/threat-intelligence/whatsapp-eternidade-trojan-self-propagates-brazil) is notable. "It's interesting that they're still hung up on banking Trojans, because a lot of time these newer threat actors are focusing on: How do we gain access to this customer's network? How do we start infiltrating exfiltrating data? How can we use ransomware to get paid?" he observes.

While banking trojans represent a direct method for financial theft, modern endpoint protections are increasingly effective at mitigating them. "I don't think most of the banking Trojans succeed at this point, in today's environment, because they're so easy to attack now," Elkins says.

Organizations with standard, up-to-date cybersecurity controls are well-positioned to defend against these campaigns. "They're getting caught more easily. I mean, Windows Defender itself has so many different rule sets for catching AutoIT executables [like those used by Water Saci] and stopping that behavior," he notes. "That's why, a lot of the time in my research, we don't see it get all the way to the end in the customer's environment. It's usually stopped at the email stage."

## About the author

Nate Nelson is a journalist and scriptwriter. He writes for "Darknet Diaries". the most popular podcast in cybersecurity — and co-created the former Top 20 tech podcast "Malicious Life." Before joining Dark Reading, he was a reporter at Threatpost.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Hasbro unauthorized access incident: Remediation and business continuity efforts</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/05282268-447a-4d14-9b63-b4d0db144a5c</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/05282268-447a-4d14-9b63-b4d0db144a5c</guid>
        <pubDate>Fri, 03 Apr 2026 03:05:19 GMT</pubDate>
        <description>Hasbro recently disclosed an unauthorized network access incident but successfully maintained key operations through proactive business continuity planning. This event illustrates the measurable value of established incident response strategies in minimizing supply chain and production disruptions.</description>
        <content:encoded><![CDATA[
            The household toys and games manufacturer Hasbro experienced a recent security incident. However, the company indicated it will continue taking orders and shipping products, though some delays may occur during remediation efforts.

In an 8-K filing with the Securities and Exchange Commission (SEC), Hasbro disclosed that on March 28 it discovered "unauthorized access" within its network. The details provided point to both immediate operational challenges and proactive resilience measures.

On the positive front, the company demonstrated preparedness for such scenarios. Unlike organizations that must fully shut down operations during major incidents, Hasbro "has implemented and continues to implement business continuity plans to enable it to continue to take orders, ship product, and conduct other key operations while it resolves this situation."

To contain the issue, Hasbro had to take certain systems offline. The company noted that these interim business continuity measures "may continue for several weeks before the situation is fully resolved and may result in some delays."

Benny Lakunishok, CEO and co-founder of Zero Networks, speculates that the incident might involve ransomware—alluding to it with the phrase "handsome mare"—and observes that the wording in Hasbro's filing warrants attention. "The fact that they said unauthorized access, and the fact that they are saying full recovery could take several weeks — those are red flags," Lakunishok adds.

## Retail sector risks

"[Retail] remains a high-value target because it combines sensitive customer data with operational complexity," says Kevin Marriott, director of cyber content strategy and IP at Immersive. "Companies like Hasbro sit across global supply chains, ecommerce platforms, and third-party ecosystems, creating a wide and often fragmented attack surface," making them frequent targets for opportunistic, financially motivated, and supply-chain-focused threat actors.

Lakunishok adds that, similar to other manufacturing entities, Hasbro prioritizes keeping production and fulfillment lines operational. "That's priority number one: they have a lot of orders, so there's a lot at stake if there's any ransomware or [disruption] of a fulfillment line. That's a lot of money [on the line], so if it's about paying $10 million, that's something they might do."

Hasbro has not specified the exact nature of the unauthorized access. The company has not yet responded to Dark Reading's request for additional details.

## Maintaining production continuity

Security incidents can severely disrupt operations, sometimes forcing production lines to halt entirely. Last year, Jaguar Land Rover experienced a ransomware incident that caused weeks of shutdowns, leading to hundreds of millions of dollars in losses for the company and affecting the broader UK economy.

In the retail sector, Marriott notes it is rare for organizations to maintain normal operations during an active security event. "There is often a significant level of disruption across logistics, customer services, payments or internal system access," he adds.

Marriott emphasizes the importance of focusing on both prevention and incident response planning. "It's about ensuring teams across an organization are prepared to both recognise and respond when something inevitably gets through. Businesses that regularly test their people through real-world simulations build the muscle memory needed to identify these tactics early and contain threats quickly."

Despite the limited details, Marriott commends Hasbro for keeping production running. "What we have seen so far from Hasbro's incident response suggests that they have effective planning and the right controls in place, which have so far enabled them to navigate a cyber incident without it escalating into a full-scale operational crisis," he observes. "This doesn't happen by accident. It's the result of organizations that have gone beyond static plans and have actively tested how they would respond under pressure."
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Threat Intelligence Update: Axios NPM Compromise, TeamPCP Cloud Operations, and Emerging MaaS Threats</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/142eba32-4cd8-4b07-9231-cf63f796a172</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/142eba32-4cd8-4b07-9231-cf63f796a172</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:53 GMT</pubDate>
        <description>This update covers recent shifts in the threat situation, including an unsafe dependency discovered in the Axios NPM package, rapid cloud enumeration by TeamPCP, and permission risks in AI agents. We detail the technical mechanics of these operations and provide actionable remediation steps to help security teams harden their environments.</description>
        <content:encoded><![CDATA[
            The current security environment is defined by a tightening loop between initial exposure and deep infrastructure compromise, driven by sophisticated supply chain methodologies and scaled social engineering. The most significant development in the past 24 hours involves a high-precision compromise of Axios, the widely used JavaScript HTTP client library. With over 400 million monthly downloads, Axios represents a critical node in the global software supply chain. Security researchers identified unauthorized versions, `axios@1.14.1` and `axios@0.30.4`—published following the compromise of a maintainer’s account. These versions introduced an unsafe dependency, `plain-crypto-js@4.2.1`, which installs a remote access trojan (RAT) across Windows and macOS systems. While registry maintainers removed the packages within hours, the incident indicates a shift in methodology: threat actors are actively staging infrastructure for long-term access brokering rather than immediate financial returns.

### Cloud enumeration and TeamPCP operations

This supply chain pressure extends directly into cloud and SaaS environments. Security teams are currently tracking a group known as TeamPCP, which has rapidly operationalized secrets exposed during recent compromises of open-source tools like the Trivy scanner and LiteLLM library. TeamPCP demonstrates high operational speed, often initiating environment discovery within 24 hours of credential exposure. The group uses validated AWS access keys and Azure secrets to perform extensive enumeration, mapping out S3 buckets and Elastic Container Service (ECS) instances. In several cases, they have utilized the ECS Exec feature to run unauthorized scripts directly on production containers, circumventing traditional perimeter controls by repurposing the organization’s own administrative tools.

### Regional trends and workforce constraints

The regional security environment in Latin America (LATAM) mirrors this intensity while facing specific structural challenges. Organizations in the region currently record nearly 40% more security incidents than the global average. Government agencies manage roughly 4,200 incidents per week, nearly double the global cross-industry average. This volume is driven by factors including the wide adoption of payment systems like Brazil’s Pix, which has led to a mature ecosystem of banking Trojans, alongside the persistence of legacy government infrastructure. At the same time, recent workforce data shows the region’s defensive capacity is restricted by rigid hiring practices. The industry faces a shortfall of 350,000 cybersecurity professionals, yet 70% of the existing LATAM workforce is self-taught, frequently lacking the formal university degrees that corporate job descriptions still mandate.

### Venom Stealer and Vertex AI permission risks

Simultaneously, the technical barriers to entry for sophisticated operations are falling due to malware-as-a-service (MaaS) platforms like Venom Stealer. This platform automates "ClickFix" social engineering campaigns, which deceive users into manually executing commands under the guise of fixing a CAPTCHA or installing a font update. Because the user initiates the execution, these techniques frequently bypass security logic designed to monitor for suspicious parent-child process relationships. Venom Stealer presents an elevated risk because it establishes a persistent exfiltration pipeline rather than performing a single credential harvesting event. It continuously monitors browser login files for new data and includes a GPU-powered engine designed to crack cryptocurrency wallet seeds found on the local filesystem. This automation enables lower-tier actors to conduct multi-stage data theft for a $250 monthly subscription.

As organizations integrate technologies like AI agents, they inherit specific permission-related risks. Security research into Google Cloud’s Vertex AI platform recently found that default configurations often grant AI agents excessive permissions through the Per-Project, Per-Product Service Agent (P4SA). In a proof-of-concept, researchers showed that an agent could be directed to extract credentials providing access to both the specific project and broader Google Workspace data, including Gmail and Drive. This over-privilege issue can transform autonomous agents into potential insider risks if teams do not strictly govern their underlying service accounts.

### Recommended defensive actions

To protect environments, the immediate priority is a thorough audit of the JavaScript build pipeline. We recommend organizations verify they have not pulled the unauthorized Axios versions. Any recent use of `axios@1.14.1` or `axios@0.30.4` should be treated as a full-system exposure, requiring complete credential rotation and forensic analysis. To counter the operational speed of groups like TeamPCP, security teams should implement active monitoring for anomalous enumeration. Specifically, monitor closely for high volumes of `git.clone` events or the unexpected use of administrative features like ECS Exec.

Mitigating the risk of "ClickFix" techniques and platforms like Venom Stealer requires adjustments to endpoint hardening. We recommend using Group Policy to restrict PowerShell execution for standard users and disabling the "Run" dialog where possible. Additionally, training programs should help employees recognize the specific mechanics of these campaigns: any web prompt asking a user to copy and paste a command into a terminal should be treated as a high-severity indicator of compromise. In cloud environments, transitioning including default AI agent permissions to a "Bring Your Own Service Account" (BYOSA) model is necessary to enforce the principle of least privilege.

### State-aligned operations and attribution

The distinction between financially motivated cybercrime and state-aligned sabotage continues and blur. Iranian state-backed groups, such as Pay2Key, increasingly adopt "pseudo-ransomware" tactics. These operations use encryption to mimic standard extortion, but the primary goal is often data destruction or political retribution. By outsourcing these operations to Russian threat actor forums through high-percentage profit-sharing models, state actors achieve a level of deniability that complicates both attribution and legal compliance for affected organizations.

While registry maintainers contained the Axios compromise relatively quickly, the full scope of the downstream impact remains unknown. The sophistication of the tradecraft—staged dependencies, multi-platform executables, and self-deleting anti-forensic measures, suggests that UNC1069, the North Korean group suspected of the operation, is refining a blueprint for future supply chain compromises. We advise security teams to maintain strict monitoring, as credentials harvested during these brief exposure windows often fuel secondary access phases weeks or months later.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Tracking the Resurgence of Pay2Key and Pseudo-Ransomware Operations</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/d84434fa-f7da-427c-b537-83384c820a19</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/d84434fa-f7da-427c-b537-83384c820a19</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:53 GMT</pubDate>
        <description>An analysis of recent intelligence detailing how state-aligned actors are leveraging pseudo-ransomware and financially motivated threat actors to obscure destructive operations. We review these evolving tactics and provide actionable guidance to help organizations protect their infrastructure and navigate associated compliance risks.</description>
        <content:encoded><![CDATA[
            State-aligned actors in Iran are establishing partnerships with participants including Russian threat actor forums and blur the boundaries between state-directed and financially motivated cyber operations. This operational shift supports their broader geopolitical objectives in the ongoing conflict involving the US and Israel.

As part of these developments, an Iranian state-backed operation known as Pay2Key has resurfaced. According to a recent report from KELA's Cyber Intelligence Center, the group is actively recruiting affiliates to target high-impact entities in the US. The methodology involves deploying "pseudo-ransomware" and operating as an initial access broker (IAB) for other ransomware groups to help disruption and financial gain.

KELA researchers note that pseudo-ransomware relies on encryption but serves primarily as a destructive tool, functioning similarly to wiper malware rather than a mechanism for standard financial extortion.

These shifts reflect a broader strategy to adopt established cybercrime methodologies following the joint US-Israel military action on February 28. KELA's analysis indicates that these operations create significant business disruption while introducing complex attribution challenges, leading to elevated legal and operational risks for affected organizations.

When an organization experiences a ransomware or extortion event, determining the identity of the threat actor becomes a critical compliance requirement. If ransom payments are inadvertently routed to state-linked entities, such as those sanctioned by the US Treasury’s Office of Foreign Assets Control (OFAC)—organizations face the risk of severe financial and legal penalties.

## Evaluating historical and current methodologies

The recent increase in Pay2Key activity parallels events from last July, following a conflict where the US and Israel targeted Iranian nuclear facilities. During that period, Pay2Key operations resumed with a focus on Western organizations, offering increased financial incentives for operations aligning with Iran’s geopolitical goals.

Currently, operators are utilizing a similar profit-sharing model. Pay2Key affiliates recruited online receive an increased share, including 70% up to 80%—when they successfully gain unauthorized access to networks belonging and designated geopolitical adversaries, primarily within the US and Israel. KELA describes this incentive structure as a method of outsourcing geopolitical operations to a broader pool of threat actors, acting as a scalable force multiplier for state-aligned activities.

Simultaneously, state-aligned groups are deploying destructive tools under the guise of financial extortion. By using ransomware-style encryption, these actors obscure data destruction, sabotage, or political retribution. For example, the Iran-backed group APT Agrius uses the Apostle malware, which researchers observed was retrofitted from its original data wiper format into a ransomware variant. Applying financial extortion frameworks over destructive wipers allows these actors to obscure their primary motives and complicates incident response efforts.

## Adapting defenses for hybrid threats

The deliberate blending of state-sponsored operations and opportunistic financial extortion means that defenders must simultaneously manage operational, financial, and geopolitical risks. Navigating this environment requires organizations to implement foundational resilience measures alongside proactive controls.

To protect organizational infrastructure against these evolving tactics, we recommend the following defensive actions:

* Apply security patches and continuously monitor internet-facing edge devices for unauthorized access.

* Deploy phishing-resistant multi-factor authentication (MFA) across the environment.

* Maintain secure, offline backups and regularly test incident response readiness.

Additionally, we advise organizations to properly segment IT and operational technology (OT) systems while hardening access controls. This structural separation reduces the risk of lateral movement by state-backed threat actors. Maintaining continuous threat intelligence monitoring will also improve an organization's visibility into adversary infrastructure and the compromised credential market, enabling faster identification of potential risks.

*Context Note: The original reporting for this intelligence was provided by Elizabeth Montalbano, a contributing writer with over 25 years of professional experience covering technology, business, and culture.*
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>TeamPCP expands unauthorized access to cloud and SaaS environments using compromised credentials</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/fc07bff1-e7d4-4dd3-85aa-1cdce0174039</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/fc07bff1-e7d4-4dd3-85aa-1cdce0174039</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:52 GMT</pubDate>
        <description>Recent supply chain incidents involving popular open source tools have led to unauthorized access across cloud and SaaS platforms. Security teams must rapidly rotate exposed credentials and monitor for anomalous enumeration activity to protect their environments.</description>
        <content:encoded><![CDATA[
            TeamPCP is leveraging compromised credentials obtained including recent supply chain incidents and access cloud and software-as-a-service (SaaS) environments.

This month, unauthorized modifications affected several open source software projects, beginning with the Aqua Security-maintained Trivy scanner and Checkmarx's KICS static code analysis tool. The threat actors subsequently compromised LiteLLM, an open source Python library, and the PyPI package of Telnyx, which developers use for voice AI agents.

Across all four campaigns, the objective remained consistent: utilize modified open source software to deploy credential-harvesting utilities within organizations. These tools are designed to collect user credentials, API keys, SSH keys, and other sensitive secrets.

TeamPCP has since escalated its operations, using these compromised credentials to gain unauthorized access to AWS and Azure environments, as well as various SaaS instances. This progression shows why rapid response protocols are necessary following supply chain exposures. Organizations that delay rotating and revoking exposed credentials face an elevated risk of unauthorized access.

## TeamPCP expands cloud access operations

In a recent security bulletin, Wiz Research detailed how its customer incident response team (CIRT) investigated and addressed multiple incidents linked to TeamPCP following the initial supply chain compromises.

The Wiz CIRT first detected the unauthorized use of credentials on March 19, observing threat actors utilizing the Trufflehog open source tool to validate the exposed secrets. The team noted validation activity targeting AWS access keys, Azure application secrets, and various SaaS tokens.

Within the affected AWS environments, the Wiz CIRT observed that the threat actors rapidly utilized the compromised secrets. Researchers noted that discovery operations began as quickly as 24 hours after the initial credential exposure.

TeamPCP conducted extensive enumeration in affected AWS environments, gathering data on identity and access management roles and S3 buckets, while specifically mapping Amazon Elastic Container Service (ECS) instances.

Following enumeration, the unauthorized parties extracted data including S3 buckets and AWS Secrets Manager. They also utilized the ECS Exec feature to execute Bash commands and Python scripts on running containers. According and Wiz researchers, this access allowed the threat actors to further map the environment and access additional sensitive data.

Wiz Research indicated to Dark Reading that while they do not provide specific figures on the number of impacted environments, the activity spans multiple cloud platforms. "What we can share is that our research shows this activity isn't limited to a single cloud," Wiz Research noted. "We've observed compromises across Azure, GitHub, and other SaaS providers, reflecting how threat actors reuse validated credentials across environments."

## The importance of rapid response

Beyond AWS environments, the Wiz CIRT documented unauthorized activity in GitHub, where TeamPCP utilized the platform's workflows to execute code in targeted repositories. The researchers noted that the threat actors also used compromised GitHub Personal Access Tokens to clone repositories at scale.

These escalating operations indicate that TeamPCP prioritizes speed over stealth. The campaigns demonstrate the necessity for swift incident response when credentials are exposed. Wiz Research stated that organizations taking immediate action to revoke or rotate access successfully limited their overall exposure.

We recommend that any organization potentially impacted by the supply chain compromises affecting Trivy, KICS, LiteLLM, or Telnyx immediately rotate all related secrets and credentials. Because threat actors may have established access to cloud instances prior to credential rotation, security teams should methodically hunt for anomalous activity within their environments.

Key indicators of suspicious activity include the unusual use of VPNs, a high volume of "git.clone" events within a short timeframe, and unexpected enumeration processes. Wiz has published specific indicators of compromise (IOCs) for the TeamPCP campaigns, and we advise security teams to monitor for these patterns while ensuring comprehensive audit logging is enabled across their infrastructure.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Securing AI agents: Addressing default permission risks in Google Cloud Vertex AI</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/fdc13099-4baf-4fb4-894d-35c8b63b126c</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/fdc13099-4baf-4fb4-894d-35c8b63b126c</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:52 GMT</pubDate>
        <description>Security research into Google Cloud’s Vertex AI platform reveals how excessive default permissions in deployed AI agents can lead to unauthorized access to sensitive data and infrastructure. Implementing a &quot;Bring Your Own Service Account&quot; (BYOSA) model allows organizations to enforce least-privilege access and safely integrate agentic AI into their environments.</description>
        <content:encoded><![CDATA[
            As organizations increasingly deploy AI agents to automate complex operational workflows, ensuring these systems are configured with appropriate permissions is a critical defensive measure. Recent security research by Palo Alto Networks details how this risk can materialize within Google Cloud's Vertex AI platform. Their analysis demonstrates that broad default permissions could enable an unauthorized party to misuse a deployed AI agent, potentially leading to unauthorized access to sensitive data and restricted internal infrastructure.

## The risk of excessive default permissions

Vertex AI is a Google Cloud platform offering an Agent Engine and Application Development Kit. Developers use these tools to build autonomous agents that interact with APIs, manage files, query databases, and execute decisions with minimal human oversight. Because these agents automate significant enterprise workflows—analyzing data, powering customer service tools, and enabling existing cloud services—they often require broad access to cloud environments.

During a security assessment, researchers identified that every deployed Vertex AI agent utilizes a default service account, known as the Per-Project, Per-Product Service Agent (P4SA), which was provisioned with excessive default permissions. If a malicious actor successfully extracts the agent's service account credentials, they could leverage these permissions to access sensitive areas of a customer's cloud environment. The research methodology demonstrated that these credentials could also grant access to Google's internal infrastructure, allowing the retrieval of proprietary container images and revealing hardcoded references to internal Google storage buckets.

## Validating the scope of access

To validate this risk, researchers developed a proof-of-concept Vertex AI agent. Once deployed, the agent queried Google's internal metadata service to extract the active credentials of the underlying P4SA service agent. These credentials provided the necessary permissions to escalate access beyond the AI agent's immediate environment, reaching the customer's broader Google Cloud Project and elements of Google's internal infrastructure.

"This level of access constitutes a significant security risk, transforming the AI agent from a helpful tool into an insider threat," wrote Palo Alto researcher Ofir Shaty in the published findings. He noted that the default scopes set on the Agent Engine could potentially extend access into an organization's Google Workspace, including services such as Gmail, Google Calendar, and Google Drive.

Ian Swanson, VP of AI security at Palo Alto Networks, emphasized the need for organizations to assess potential risks before deployment and protect agents during runtime. “Agents represent a shift in enterprise productivity including AI that talks and AI that acts,” he stated, noting that this shift introduces risks of unauthorized actions alongside traditional data exposure concerns.

## Implementing least-privilege access

Following the disclosure of these findings, Google updated its official documentation to clarify how Vertex AI uses agents and resources. To secure agentic AI environments, Google recommends that organizations replace the default service agent on Vertex Agent Engine with a custom, dedicated service account.

A Google spokesperson emphasized this approach as a primary defense mechanism. "A key best practice for securing Agent Engine and ensuring least-privilege execution is Bring Your Own Service Account (BYOSA)," the spokesperson stated. "Using BYOSA, Agent Engine users can enforce the principle of least privilege, granting the agent only the specific permissions it requires to function and effectively mitigating the risk of excessive privileges."

## About the original reporting

This security bulletin preserves the factual reporting originally authored by Jai Vijayan, a contributing writer and technology reporter with over 20 years of experience in IT trade journalism. Previously a Senior Editor at Computerworld covering information security, data privacy, big data, Hadoop, the Internet of Things, e-voting, and data analytics, Vijayan also covered technology for The Economic Times in Bangalore, India. He holds a Master's degree in Statistics and resides in Naperville, Illinois.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Unauthorized Modifications Identified in Axios NPM Package</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/3422bdcc-63b6-4a82-96f4-d870d18a5e5c</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/3422bdcc-63b6-4a82-96f4-d870d18a5e5c</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:50 GMT</pubDate>
        <description>Security researchers identified two unauthorized versions of the popular Axios NPM package that introduced a remote access trojan (RAT) through a hidden dependency. Organizations using Axios should review their dependency logs for specific indicators of compromise and verify their recent installation pipelines.</description>
        <content:encoded><![CDATA[
            The Axios JavaScript NPM package recently experienced a software supply chain security incident. As the most widely used JavaScript HTTP client library, downloaded over 400 million times per month, this event demonstrates the practical need for strict dependency validation across development environments.

Software development security vendor StepSecurity identified that two unauthorized versions of the library had been published to the NPM registry: `axios@1.14.1` and `axios@0.30.4`.

These versions introduced a new, unverified dependency named `plain-crypto-js@4.2.1`. Masquerading as the legitimate `crypto-js` library, this package executes a script that installs a remote-access trojan (RAT) compatible with Windows, Linux, and macOS systems. Researchers trace the origin of the incident to unauthorized access to the lead maintainer's account, "jasonsaayman."

"The dropper contacts a live command-and-control server and delivers platform-specific, second stage payloads. After execution, the malware deletes itself and replaces its own package.json with a clean version to evade forensic detection," StepSecurity explained in its analysis. "There are zero lines of malicious code inside axios itself, and that's exactly what makes this attack so dangerous."

The unauthorized packages remained active for approximately three hours before NPM removed all traces of the campaign. However, Endor Labs noted that one version of the `plain-crypto-js` dependency was publicly exposed for more than 21 hours before registry maintainers applied a security hold. Because the software is heavily adopted, organizations should check their environments for indicators of compromise (IOCs) published by StepSecurity, Endor Labs, and Socket.

Feross Aboukhadijeh, CEO of Socket, recommends that teams using the JavaScript ecosystem should pause standard operations and verify their dependencies immediately to ensure their environments remain secure.

## Threat Actor Motivations and Attribution

Determining the origin of supply chain incidents requires careful observation of post-installation behavior. Early industry reports suggested a link to TeamPCP, a group associated with cloud-native unauthorized access and ransomware. However, Google Threat Intelligence subsequently issued a statement attributing the activity to suspected North Korean threat actor UNC1069.

Google Threat Intelligence Group chief analyst John Hultquist stated that the full scope of the incident remains under investigation, but the organization expects the downstream impact to be significant.

Ashish Kurmi from StepSecurity observed that the trojan's operational pattern points toward access brokering or targeted espionage rather than rapid credential theft.

"The RAT's first action is device profiling (hostname, username, OS, processes, directory walk) before doing anything else — that's cataloging, not looting. A blunt infostealer grabs credentials and leaves; this one fingerprints the environment and waits for instructions," Kurmi says. "Axios lives in developer environments holding source code, deploy keys, and cloud credentials a cryptominer has no use for, and the 18-hour pre-staging, simultaneous branch poisoning, and anti-forensics suggest an actor who has done this before."

If UNC1069 is responsible, this represents a notable shift in their operational methodology. The group operates as an arm of North Korea's Lazarus Group, which historically targets cryptocurrency wallets and fintech infrastructure. A verified link would mark their first successful compromise of a top-tier NPM package.

## Advanced Operational Tradecraft in the Open Source Supply Chain

The open source supply chain has seen multiple security events in recent months, including the Shai-hulud and GlassWorm incidents. While those relied on opportunistic propagation, researchers categorize the Axios incident as highly precise.

"The malicious dependency was staged 18 hours in advance. Three payloads were pre-built for three operating systems. Both release branches were poisoned within 39 minutes of each other. Every artifact was designed to self-destruct," StepSecurity reported. "Within two seconds of npm install, the malware was already calling home to the attacker's server before npm had even finished resolving dependencies. This is among the most operationally sophisticated supply chain attacks ever documented against a top-10 npm package."

Kurmi points out that executing this required more than standard typosquatting techniques. The threat actor had to gain access to a verified maintainer account, bypass the Axios project's OIDC-based publishing pipeline, and implement anti-forensic measures to manipulate `npm list` reports post-installation.

He places this incident along a continuum of increasing operational awareness, alongside recent compromises involving Nx Singularity, tj-actions/changed-files, Trivy, Checkmarx KICS, LiteLLM, and the Canister worm.

From a defender's perspective, the brief three-hour primary exposure window naturally limited total installations. However, the silent execution model means developers impacted during that timeframe would not have received standard error warnings or system alerts. A quiet, traceless execution presents a fundamentally different operational risk than a loud failure that prompts immediate remediation.

Peyton Kennedy, a security researcher at Endor Labs, observes that the methods used in this incident demonstrate a clear escalation in supply chain methodology.

"Last year, Shai-hulud's worm-based propagation was novel, and we've since seen that technique replicated in CanisterWorm and other campaigns," Kennedy says. "This attack is a different kind of escalation: staged dependency seeding to evade scanners, platform-specific payload chains, and self-deleting anti-forensic cleanup. This looks like deliberate, planned tradecraft from an experienced threat actor."
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Venom Stealer platform automates ClickFix social engineering and data exfiltration</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/4a02f922-ddd3-4cbd-918b-4831cc91e91c</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/4a02f922-ddd3-4cbd-918b-4831cc91e91c</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:49 GMT</pubDate>
        <description>Security researchers have identified Venom Stealer, a malware-as-a-service platform that automates ClickFix social engineering campaigns and cryptocurrency theft. The platform combines deceptive user prompts with continuous data exfiltration, emphasizing the need for organizations to strengthen endpoint execution controls and monitor outbound traffic.</description>
        <content:encoded><![CDATA[
            Managing exposure to ClickFix-style social engineering campaigns requires understanding how these threats are evolving. Recently, security researchers at BlackFog identified a newly distributed malware-as-a-service (MaaS) platform that automates the technical steps of these campaigns for threat actors.

Operating under the name "VenomStealer," the developer offers a MaaS platform on cybercriminal networks that allows operators to create a persistent, multistage execution flow. Based on the initial ClickFix user interaction, the software automates unauthorized access to credentials, cryptocurrency wallets, and ongoing data exfiltration.

According to BlackFog founder and CEO Darren Williams, Venom differentiates itself from commodity stealers like Lumma, Vidar, and RedLine by extending beyond a single credential harvesting event. The platform integrates ClickFix social engineering directly into its operator panel, automating the post-access sequence and establishing a continuous exfiltration pipeline that remains active after the initial execution package finishes running.

Marketed on cybercriminal forums as "the Apex Predator of Wallet Extraction," the platform operates on a subscription model, costing $250 a month or $1,800 for lifetime access. The operation includes a vetted application process, Telegram-based licensing, and a 15% affiliate program. The delivery mechanism relies on a native C++ binary compiled per-operator directly from the web panel.

Unlike traditional infostealers that execute once, transmit data, and exit, Venom Stealer continuously scans the affected system. It harvests credentials, session cookies, and browser data while targeting cryptocurrency wallets and stored secrets. The platform also automates wallet cracking and fund draining. The operation appears highly active, with the developer shipping multiple platform updates throughout March alone.

## Step-by-step ClickFix execution

A campaign built with Venom Stealer begins when an individual lands on a deceptive ClickFix page hosted by the operator. The platform includes four templates for both Windows and macOS environments: a fake Cloudflare CAPTCHA, a fake OS update, a simulated SSL certificate error, and a fake font installation page. Each template instructs the user to open a Run dialog or Terminal window, copy and paste a specific command, and press Enter.

Because the user initiates the execution manually, the process appears as normal user activity, which frequently bypasses detection logic that relies on evaluating parent-child process relationships.

Available Windows execution packages in the kit include.exe,.ps1 (enabling fileless execution via PowerShell),.hta, and.bat options. For macOS environments, the templates utilize bash and curl. The platform allows operators to configure custom domains through Cloudflare DNS, ensuring the panel URL remains hidden from the command string copied by the user.

Once executed, the software scans every Chromium and Firefox-based browser on the machine. It extracts saved passwords, session cookies, browsing history, autofill data, and cryptocurrency wallet vaults across all browser profiles.

The execution sequence also includes specific evasion capabilities. For instance, the password encryption in versions 10 and 20 of Chrome is bypassed using a silent privilege escalation technique. This extracts the decryption key without triggering a user account control (UAC) dialog, minimizing forensic artifacts. Additionally, the software captures system fingerprinting and browser extension inventories, compiling a comprehensive profile of the affected user.

This collected data leaves the infected device immediately, with little to no local staging or delay. Without adequate visibility into outbound network traffic, detecting this extraction phase is significantly more difficult for security teams.

## Persistent data exfiltration pipeline

Upon discovering wallet data, the software transfers it to a server-side, GPU-powered cracking engine. This engine automatically cracks cryptocurrency wallets, including MetaMask, Phantom, Solflare, Trust Wallet, Atomic, Exodus, Electrum, Bitcoin Core, Monero, and Tonkeeper. A March 9 update to the platform introduced a File Password and Seed Finder, which searches the local filesystem for saved seed phrases and feeds any discovered data into the cracking pipeline.

Consequently, users who avoid saving credentials directly in their browsers still face exposure if seed phrases are stored anywhere on their local machine.

While some newer infostealer variants include persistence mechanisms, Venom Stealer maintains an active presence after the initial compromise. It continuously monitors Chrome’s Login Data file, capturing newly saved credentials in real-time. This mechanism undermines standard credential rotation as an incident response measure and extends the data exfiltration window, making it more challenging for security teams to determine the full scope of a security incident.

## Reducing exposure to ClickFix campaigns

Security researchers from Proofpoint first identified ClickFix techniques roughly two years ago, and the methodology has since gained significant traction. The technique relies on instilling a sense of urgency—prompting users to fix an error or install an update—while using familiar, benign interfaces like CAPTCHA prompts to create a false sense of security. The primary goal is to trick the user into manually executing unauthorized commands.

Organizations can safeguard their environments and reduce exposure to threats like Venom Stealer by implementing several preventative controls:

* Restrict PowerShell execution: Limit access to PowerShell for standard users and enforce strict execution policies.

* Disable the Run dialog: Use Group Policy to remove the Run dialog for non-administrative users.

* Enhance security awareness: Train employees to recognize ClickFix-style social engineering, specifically the danger of copying and pasting commands from web prompts into terminals.

* Monitor outbound traffic: Because the sequence relies on data leaving the device, monitoring and controlling outbound traffic provides a critical opportunity to detect exfiltration activity and mitigate the impact of credential theft.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Security incidents increase pressure on Latin American government agencies</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/76edb046-f2a5-4ee2-9353-5636dd0665a4</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/76edb046-f2a5-4ee2-9353-5636dd0665a4</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:49 GMT</pubDate>
        <description>Government organizations in Latin America are navigating an elevated volume of security threats targeting public infrastructure. Assessing the structural factors behind this trend reveals clear, actionable steps agencies can take to secure legacy systems and protect citizen data.</description>
        <content:encoded><![CDATA[
            Government organizations across Latin America and the Caribbean are managing a heightened volume of security incidents targeting critical agencies at rates exceeding global averages. Recent events include unauthorized access attempts against a national health agency in Colombia, a security incident affecting Puerto Rico's transportation department, and threat actors utilizing AI systems to target Mexico's government infrastructure.

In March, organizations in Latin America recorded an average of 3,050 security incidents per week, compared to a global average of just over 2,000, according to data from Check Point Software Technologies. Government agencies face even higher exposure, recording nearly 4,200 incidents weekly—approximately 1,000 more than the cross-industry average, notes Angel Salazar, security engineering manager for the Latin American region at Check Point.

Salazar explains that government networks typically experience constant exposure due to public services that must remain online, legacy systems that are difficult to replace, and high user turnover. Together, these factors create a continuous external digital footprint.

March saw several high-profile security disclosures in the region. Early in the month, unauthorized groups compromised at least nine government agencies in Mexico using major AI systems, potentially accessing more than 195 million identities and tax records. Colombia's health ministry, the Superintendencia Nacional de Salud (Supersalud), reported managing more than 23 million unauthorized probes during the month in a March 27 notification addressing system security. Last week, Puerto Rico's Department of Transportation temporarily halted driver's license issuance following a security incident that was ultimately contained, according to statements the agency provided to the media.

While financially motivated groups drive the majority of these incidents, nation-state espionage and politically motivated activity present growing risks, according to Camilo Gutiérrez, field chief information security officer for ESET's Argentina Country Office.

Gutiérrez observes that while the most probable risk for daily government operations remains financial, state-related or hybrid activity has grown into a strategic concern that requires dedicated attention.

## Phishing and credential exposure

Latin America has transitioned into one of the most heavily targeted regions globally, with government agencies consistently remaining a primary focus, says Tom Hegel, a distinguished threat researcher at SentinelOne.

The region faces a mature banking-Trojan ecosystem and a rise in information stealers, which harvest credentials to support initial-access broker services.

"The region has a massive exposed credential problem," Hegel explains. "Billions of credentials are circulating through Telegram channels and dark web markets. Infostealers harvest them, initial-access brokers package and sell the access, and ransomware affiliates buy their way in."

Email serves as the primary delivery channel for unauthorized activity. According to Salazar, approximately 82% of unsafe files arrive via email in Latin America, compared to a 56% rate globally. Threat actors generally follow familiar paths, with phishing remaining the primary method for gaining initial access. Additionally, unauthorized parties actively look for exposed public-facing services connected to the internet, many of which rely on older platforms.

## Structural challenges and paths to remediation

Securing legacy technology remains a complex challenge for many government organizations, often complicating patch management. Threat actors frequently scan for unpatched software, while local agencies work to maintain older systems, Gutiérrez explains.

Additionally, Latin American institutions face a shortage of skilled cybersecurity professionals and the operational capabilities required to maintain IT infrastructure. Gutiérrez points to a World Bank report indicating a regional shortfall of about 350,000 cybersecurity professionals. Less specialized personnel directly translates to reduced system hardening, gaps in monitoring, and slower response times.

Salazar notes that the public sector's challenges are often structural, involving older systems, uneven patching processes, small security teams, and complex supplier relationships.

To strengthen their defensive posture, organizations should begin by securing email environments, the most common entry point. Following this, continuous monitoring of the external digital footprint helps teams identify previously unknown vulnerable assets. Because government agencies act as custodians of citizen data, prioritizing efforts to reduce data exposure and minimize leakage is essential.

Salazar emphasizes that government agencies must maintain real-time visibility into their exposed infrastructure, accurately assess operational risks, and prioritize the remediation of vulnerabilities most likely to be targeted.

## About the author

Robert Lemos is a veteran technology journalist with over 20 years of experience and a former research engineer. He has written for numerous publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. He has received five journalism awards, including Best Deadline Journalism (Online) in 2003 for coverage of the Blaster worm. He analyzes industry trends using Python and R, with recent reports focusing on the cybersecurity workforce shortage and annual vulnerability trends.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Expanding the Cybersecurity Talent Pool in Latin America to Meet Growing Security Needs</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/6503c969-c5c3-499a-9fb6-cc7c1d5e01bd</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/6503c969-c5c3-499a-9fb6-cc7c1d5e01bd</guid>
        <pubDate>Thu, 02 Apr 2026 03:27:48 GMT</pubDate>
        <description>A recent survey of Latin American security practitioners reveals a largely self-taught workforce. By adjusting hiring expectations and supporting non-traditional learning paths, organizations can better staff their teams and defend against regional threat activity.</description>
        <content:encoded><![CDATA[
            To effectively staff cybersecurity teams, organizations in Latin America have a clear mandate to expand their search and engage the region's diverse, non-traditional talent pool. This adjustment is increasingly necessary as local threat activity outpaces global averages, requiring well-resourced teams to maintain solid defense postures.

These findings stem from an employment report released by Ekoparty, an annual cybersecurity conference hosted in Buenos Aires and Miami. The organization shared its analysis, based on a survey of 605 Latin American security professionals, to identify structural hiring challenges and offer practical guidance for security leaders looking to grow their teams.

Latin American organizations experience roughly 40% more security incidents than the global average, requiring proactive defense strategies tailored to the region. The security requirements in these countries are highly specific. For example, Brazil successfully deployed its standardized Pix mobile payment system in 2020. While a major technological advancement, the platform's wide adoption introduced new security demands, as the system became a frequent target for banking Trojans and phishing campaigns. The availability of automated threat tools that require minimal technical knowledge has further complicated this environment. Relying solely on traditional, formal talent pipelines is no longer sufficient to manage these specific risks and ensure organizational resilience.

## A community built on self-directed learning and independent research

Many organizations assume that technical security roles require formal university degrees. However, the survey data shows a different reality: 70% of respondents developed their capabilities through informal pathways, such as online courses and hands-on experience. Only 44% hold a university degree, and roughly half (53%) possess at least one industry certification.

Work arrangements within the community also differ from traditional corporate expectations. While 79% of respondents work in full-time roles, 44% maintain a second, related occupation. These secondary roles frequently include security research, teaching, or participating in vulnerability reward programs. Security professionals often split their time across different community projects, a reality that hiring organizations can accommodate to attract highly skilled individuals.

These data points indicate substantial, underutilized opportunities for security leaders to connect with a broader segment of the practitioner community.

This is particularly relevant for entry-level professionals. About 35% of respondents had fewer than three years of experience. This is a critical metric for hiring managers to consider, given that many job descriptions request a decade of experience for roles that could be filled by developing practitioners. Furthermore, women enter the security field between seven and 10 years later than men on average. Addressing the structural barriers that cause this delay provides a direct path to expanding the talent pool and building more capable, diverse teams.

## Fostering developing talent

While security budgets often require careful management, financial compensation is not the only factor candidates evaluate when considering an employer. The survey shows that professionals highly value employee well-being, flexible work arrangements (such as remote or hybrid schedules), recognition of their expertise, and job stability. By prioritizing these elements, organizations can build appealing environments for candidates while remaining conscious of financial constraints.

"Ultimately, while cybersecurity demands a high level of expertise and commitment, professionals in Latin America are equally driven by the desire to build meaningful and sustainable careers within a rapidly evolving industry," the report noted.

Federico Kirschbaum, a co-founder of Ekoparty, observed that the industry often struggles with a cyclical hiring problem. Organizations frequently require 10 or more years of experience for early security hires, but offer compensation misaligned with that level of seniority. This mismatch deters qualified candidates and leaves security teams understaffed if organizations cannot adjust their salary bands.

To resolve this, companies can meet professionals where they are by fostering developing talent and integrating with the community.

"Our pitch is, Hey, I think there are many people in this industry that come from an informal background in terms of learning," Kirschbaum says. "They are proficient. They are not here only for the money, but also because they really love what they do. But to an extent, we need to make companies aware that if you want to grab this talent, you also need to retune your hiring so you are part of the learning experience. I think talent is being formed not only from the academia but also from the industry."

## About the author

Alexander Culafi is a Senior News Writer based in Boston. After beginning his career writing for independent gaming publications, he graduated from Emerson College in 2016 with a Bachelor of Science in journalism. He has previously been published on VentureFizz, Search Security, Nintendo World Report, and elsewhere. In his spare time, Alex hosts a weekly podcast and works on personal writing projects, including two previously self-published science fiction novels.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Evaluating the reported zero-click vulnerability in Telegram</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/c5286035-58b3-4ded-8e8d-9870bd7f0f89</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/c5286035-58b3-4ded-8e8d-9870bd7f0f89</guid>
        <pubDate>Tue, 31 Mar 2026 03:13:26 GMT</pubDate>
        <description>Security researchers and Telegram are currently examining a reported zero-click vulnerability (ZDI-CAN-30207) potentially affecting Android and Linux clients. We outline the technical claims, the vendor&apos;s response, and practical steps organizations and individuals can take to safeguard their communications.</description>
        <content:encoded><![CDATA[
            Security researchers are actively evaluating a reported vulnerability in Telegram Messenger that could lead to full system compromise. Full technical details of the unpatched vulnerability are scheduled for disclosure in July.

The vulnerability, which could impact a significant portion of the application's 1 billion users, was discovered by Michael DePlante of the Trend Micro Zero Day Initiative (ZDI). ZDI disclosed the existence of the finding, tracked as ZDI-CAN-30207, on Thursday and scheduled a full disclosure date for July 26.

Telegram has publicly denied the vulnerability's existence on the social media platform X. This differing assessment has generated considerable discussion across security communities, as researchers and users work to evaluate the actual risk.

ZDI initially assigned the vulnerability a 9.8 CVSS score. On Monday, the organization lowered the score to a high-severity 7.0. In a follow-up post on X, ZDI clarified that the adjustment was made to reflect "server-side mitigations that the vendor described during the disclosure process."

While full technical specifics remain restricted until July 26, various published alerts provide insight into the initial severity rating. According to an advisory published by Italy's National Cybersecurity Agency, ZDI-CAN-30207 enables a suspected zero-click, network-based compromise on Android and Linux versions of the application. If successfully triggered, the vulnerability could allow an unauthorized party to execute arbitrary code, access private communications, conduct surveillance, access sensitive data, and disrupt device functionality.

## The role of animated stickers

Triggering the reported vulnerability involves sending a specially crafted animated sticker. Stickers are media files used within the application to convey emotions or replace standard text messages.

Independent cybersecurity consultant Carolina Vivianti noted in a Red Hot Cyber blog post that the method is remarkably simple, relying entirely on these animated files. She highlighted the finding as concerning because the compromise sequence requires no user interaction.

"Simply receiving the content is enough," Vivianti wrote. "No confirmation, no user interaction. The system processes the files to generate previews, and it is precisely during this stage that the [unauthorized execution] occurs."

Telegram has repeatedly stated that compromising the application via stickers is not possible. The company asserted that the claim "completely disregards that all stickers uploaded to Telegram are validated by its servers before they can be played by Telegram apps."

Italy's National Cybersecurity Agency subsequently updated its alert to include Telegram's denial. The agency noted Telegram's official position that the centralized filtering process prevents corrupted stickers from reaching the end user, making remote code execution technically impossible through this method.

## Context and platform risks

Because Telegram utilizes message encryption, it serves as a primary communication tool for users requiring privacy. A zero-click vulnerability allowing unauthorized parties to access data or conduct surveillance would represent a substantial risk to the platform's user base.

Threat actors frequently evaluate messaging applications to target specific individuals whose communications hold strategic value, including journalists, government officials, and enterprise users.

Telegram's broader security and data policies have also drawn recent scrutiny. In 2024, French authorities arrested CEO Pavel Durov over the company's historical refusal to share data with law enforcement agencies, leading the platform to adjust its policies. Additionally, unauthorized parties often use the application to coordinate activities, frequently establishing dedicated channels as operational infrastructure.

## Defensive measures

Until the public disclosure in July provides definitive technical clarity, users and organizations should prioritize standard application maintenance. Telegram users should apply all app updates as they are released in the coming months to ensure they are operating the most current and secure version.

For those requiring immediate risk reduction, Vivianti proposes specific defensive actions. For business users, she recommends restricting message reception to trusted contacts or Premium users to minimize exposure. "This clearly affects communication workflows, but it lowers the exposure risk," Vivianti noted.

For general users, simply disabling automatic downloads is insufficient. Instead, Vivianti recommends temporarily utilizing the Web version of Telegram through an up-to-date browser, which leverages modern browser sandboxing. This approach provides a stronger isolation layer compared to the native client. Alternatively, users may choose to temporarily uninstall the native application until further details are verified.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>F5 BIG-IP vulnerability CVE-2025-53521 reclassified as RCE and actively targeted</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/6b23c7d0-8ad9-40c3-9ac0-71b404d8d225</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/6b23c7d0-8ad9-40c3-9ac0-71b404d8d225</guid>
        <pubDate>Tue, 31 Mar 2026 03:13:25 GMT</pubDate>
        <description>A vulnerability in F5&apos;s BIG-IP Access Policy Manager has been reclassified including a denial-of-service issue and a critical remote code execution flaw. With active targeting observed in the wild, organizations are advised to prioritize updates and review indicators of compromise.</description>
        <content:encoded><![CDATA[
            Security researchers and network defenders are tracking an escalated risk regarding F5's BIG-IP application security product line. A vulnerability in the BIG-IP Access Policy Manager (APM), originally identified in October 2025 as a high-severity denial-of-service (DoS) issue, has been reclassified as a critical remote code execution (RCE) vulnerability. F5 confirms the flaw is currently being targeted in the wild.

F5 updated its security advisory on Saturday, designating CVE-2025-53521 as an RCE flaw with a CVSS v3.1 score of 9.8. When initially disclosed and patched on October 15, the issue carried a CVSS score of 7.5. The vendor cited "new information obtained in March 2026" as the basis for the elevated severity rating, though the specific technical details of that new information have not been publicly detailed.

## Technical details and affected versions

According to F5's documentation, an unauthorized party can leverage this vulnerability by sending "specific malicious traffic" to virtual servers configured with BIG-IP APM. Successful utilization grants remote code execution capabilities on the affected device.

The exposure affects BIG-IP APM versions 17.5.0 to 17.5.1, 17.1.0 to 17.1.2, 16.1.0 to 16.1.6, and 15.1.0 to 15.1.10. F5 notes that BIG-IP systems operating in appliance mode, a configuration designed to restrict administrative access to the systems, remain vulnerable to this flaw.

## Indicators of compromise and scanning activity

The US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2025-53521 to its Known Exploited Vulnerabilities (KEV) catalog on Friday. To assist security teams with detection and incident response, F5 published indicators of compromise (IoCs) related to this activity.

Organizations evaluating their systems should monitor for a specific software tool tracked as c05d5254. System anomalies indicating unauthorized access may include the presence of unexpected files on disk, specifically `/run/bigtlog.pipe` and `/run/bigstart.ltm`. Defenders should also verify the file sizes, hashes, and timestamps of `/usr/bin/umount` and `/usr/sbin/httpd` against known good configurations, as mismatches indicate potential modification.

Security firm Defused reported observing scanning activity targeting this vulnerability shortly after its addition to the CISA KEV catalog. In a public update on the social media platform X, Defused noted that unauthorized scanning frequently targets the `/mgmt/shared/identified-devices/config/device-info` endpoint. This specific BIG-IP REST API endpoint returns system-level information, including hostnames, machine IDs, and base MAC addresses.

Simo Kohonen, founder and CEO of Defused, stated that while their BIG-IP honeypot infrastructure regularly records unauthorized access attempts, the recent activity shows distinct changes in how threat actors fingerprint F5 instances.

"Generic mass exploiters consistently use the same type of payload, but we've observed minor deviations to the payloads in the past week, which suggests more actors out there are looking at mapping out F5 infrastructure," Kohonen said.

## Remediation and next steps

F5 infrastructure remains a high-value target for threat actors mapping enterprise perimeters. Last year, state-sponsored groups gained unauthorized access to F5 systems, resulting in the exposure of sensitive data that included source code for the BIG-IP platform.

Given the reclassification and active targeting of CVE-2025-53521, organizations should prioritize upgrading vulnerable BIG-IP APM instances to a fixed version. Security teams must also review system logs and file integrity based on the provided IoCs to ensure no unauthorized access has occurred prior to patching.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>DeepLoad credential stealer uses AI-generated padding and ClickFix delivery to evade static detection</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/b02aadc1-d209-4e37-b7d4-b4f262ac858a</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/b02aadc1-d209-4e37-b7d4-b4f262ac858a</guid>
        <pubDate>Tue, 31 Mar 2026 03:13:24 GMT</pubDate>
        <description>Security researchers have identified DeepLoad, a new malware strain that captures credentials immediately upon execution and uses process injection to evade static scanning. To fully remediate affected hosts, organizations must look beyond standard file cleanup and address persistent WMI event subscriptions.</description>
        <content:encoded><![CDATA[
            Security researchers have analyzed a new malware strain tracked as DeepLoad, which is capable of capturing credentials immediately after gaining a foothold on a network. The malware relies on a standalone stealer and an unsafe browser extension to capture both stored browser passwords and live keystrokes in real time.

According to ReliaQuest, DeepLoad presents unique containment challenges due to its likely use of AI-generated code for evasion and process injection techniques that bypass static detection. It also establishes a persistence mechanism that can silently re-execute the execution chain even after an affected host appears fully remediated.

## DeepLoad delivery via ClickFix

DeepLoad operators distribute the credential stealer across enterprise environments using the ClickFix social engineering technique. This method begins with affected users receiving fake browser prompts that ask them to execute a seemingly benign command to resolve a fabricated system error.

When executed, this command immediately creates a scheduled task to re-execute the loader. This ensures the unauthorized access persists across system reboots or partial detection without any further user interaction. The sequence then uses mshta.exe, a legitimate Windows utility, to communicate with external infrastructure and download a heavily obfuscated PowerShell loader.

Because DeepLoad captures credentials from the moment it lands, even partial containment can leave an organization with exposed passwords, active session tokens, and compromised accounts. Before the primary execution chain finishes, a standalone credential stealer named filemanager.exe begins running on its own infrastructure. This component can exfiltrate data even if the main loader is subsequently detected and blocked. Additionally, the malware drops and registers a browser extension that captures credentials as users type them, persisting across browser sessions until explicitly removed.

## Heavily padded loader and process injection

Analysis of DeepLoad indicates that its functional code is hidden beneath thousands of lines of irrelevant code. This volume of padding appears specifically designed to overwhelm static scanning tools, leaving them with no identifiable signatures to flag. The scale and structure of this padding suggest it was likely developed by an AI model rather than a human programmer.

DeepLoad’s core logic consists of a short decryption routine that unpacks its active component entirely in memory. Once unpacked, this component is injected into LockAppHost.exe, a legitimate Windows process that manages the lock screen. Security tools typically do not actively monitor this process, making it an effective location for unauthorized activity.

To carry out the injection, DeepLoad leverages a PowerShell feature called Add-Type to generate a temporary Dynamic Link Library (DLL), which is then dropped into the affected computer's Temp directory. The malware compiles this DLL freshly on every execution, assigning it a randomized filename to ensure that security tools scanning for specific indicators will not find a match. The sequence also disables PowerShell command history to obscure its tracks.

During the evaluated campaign, DeepLoad also demonstrated lateral movement capabilities by spreading to connected USB drives within 10 minutes of the initial infection. The malware wrote more than 40 files to the USB drive of the affected host, disguising them as familiar installers for applications like Chrome, Firefox, and AnyDesk. This mechanism increases the likelihood of a user executing one of the deceptive installers and exposing another machine. It remains unclear whether USB propagation is a permanent feature of DeepLoad or a modular addition for this specific campaign.

## Standard remediation is not enough

Standard cleanup procedures—such as removing scheduled tasks, temporary files, and familiar indicators of compromise (IOCs)—are not sufficient to fully remediate DeepLoad. The malware creates a persistent trigger within Windows Management Instrumentation (WMI) that automatically reruns the sequence without any further user interaction. In one investigated incident, this mechanism re-executed the unauthorized access a full three days after the affected host appeared to be thoroughly cleaned.

To properly secure affected environments, organizations must audit and remove WMI event subscriptions on exposed hosts before returning them to production. Security teams should enable PowerShell Script Block Logging and behavioral endpoint monitoring to identify unauthorized activity, as traditional file-based scanning will not detect the padded loader. Furthermore, organizations must rotate all credentials associated with an affected system, including saved passwords, active session tokens, and accounts that were in use during the exposure period.

The evidence of AI-generated code suggests a realistic probability that obfuscation techniques will evolve from generic noise to padding tailored specifically to the targeted environment. As WMI subscriptions are added to standard remediation checklists, threat actors will likely shift their persistence mechanisms to other legitimate Windows features that currently receive less scrutiny.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Evaluating recent shifts in persistence: F5 APM reclassification and DeepLoad evasion techniques</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/f0df3405-4885-4ec0-833f-a254c71d6c53</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/f0df3405-4885-4ec0-833f-a254c71d6c53</guid>
        <pubDate>Tue, 31 Mar 2026 00:00:00 GMT</pubDate>
        <description>Unauthorized actors are increasingly adapting their persistence and evasion methods, utilizing AI-generated code to bypass static analysis and targeting newly reclassified perimeter vulnerabilities. This report details the technical mechanisms behind the DeepLoad credential-theft malware and the escalation of CVE-2025-53521 in F5 BIG-IP systems, providing actionable guidance to protect enterprise environments.</description>
        <content:encoded><![CDATA[
            Security researchers are working with defense teams to address a shift in how unauthorized parties achieve persistence and evade detection. This activity ranges including the use of AI-generated obfuscation and the targeting of reclassified perimeter vulnerabilities. A primary concern for enterprise environments involves an elevated risk profile for F5 BIG-IP systems. Originally disclosed as a denial-of-service issue last October, a vulnerability in the BIG-IP Access Policy Manager (APM) was reclassified this morning as a critical remote code execution (RCE) flaw. Tracked as CVE-2025-53521 with a CVSS score of 9.8, the vulnerability is involved in active security incidents, prompting its addition to the CISA Known Exploited Vulnerabilities catalog.

This escalation aligns with the discovery of DeepLoad, a malware strain that uses AI-generated code to bypass standard security layers. DeepLoad represents an evolution in credential theft, relying on a "ClickFix" social engineering technique to gain initial access. When a user executes a command to resolve a simulated system error, the software immediately captures credentials and establishes a foothold that requires precise remediation to remove. The emergence of DeepLoad and the targeted activity against F5 perimeters point to coordinated efforts to compromise both network edges and end-user workstations.

Technically, DeepLoad relies on highly specific evasion and persistence mechanisms. To bypass static scanning, it hides its functional logic beneath thousands of lines of irrelevant, AI-generated padding. This volume of data overwhelms signature-based tools, which struggle to identify the core decryption routine. Once active, DeepLoad unpacks entirely in memory and injects its core components into `LockAppHost.exe`, a legitimate Windows process responsible for the lock screen. Because security tools rarely monitor this specific process for unauthorized activity, the software operates with high stealth.

Defenders should evaluate DeepLoad’s persistence strategy carefully. Beyond standard scheduled tasks, it creates a persistent trigger within Windows Management Instrumentation (WMI). This ensures that even if a host appears remediated through the removal of files or scheduled tasks, the software can re-execute the entire sequence days later. In one investigated instance, the activity re-triggered three days after an initial cleanup effort. Furthermore, the malware uses a PowerShell feature called `Add-Type` to compile a temporary, randomly named DLL in the Temp directory upon every execution, making file-based indicators a moving target. Lateral movement is also a core capability; DeepLoad can spread to connected USB drives in as little as ten minutes, disguising its components as legitimate installers for applications like Chrome or AnyDesk.

Simultaneously, the threat situation at the network perimeter requires attention following the reclassification of CVE-2025-53521. F5 updated its advisory after receiving new data showing that unauthorized parties can achieve RCE by sending specific traffic to virtual servers configured with BIG-IP APM. This vulnerability affects multiple versions, including 15.1.x, 16.1.x, 17.1.x, and 17.5.x, and impacts systems running in appliance mode. Monitoring activity suggests that malicious actors are moving including generic mass scanning and focused fingerprinting of F5 infrastructure. Researchers have observed unauthorized scanning of the `/mgmt/shared/identified-devices/config/device-info` REST API endpoint, which is used to map machine IDs and hostnames.

Regarding secure communications, researchers are evaluating a reported zero-click vulnerability in Telegram. Tracked as ZDI-CAN-30207, the flaw reportedly allows for system compromise on Android and Linux clients through the receipt of a specially crafted animated sticker. While the Zero Day Initiative (ZDI) recently lowered the severity score including 9.8 to 7.0 and account for server-side mitigations, the core risk remains: the vulnerability reportedly triggers during the preview generation process, requiring no user interaction. Telegram has stated that their server-side validation prevents corrupted stickers from reaching users. However, Italy’s National Cybersecurity Agency has advised caution until full technical details are disclosed in late July.

These developments require a multi-layered response to protect systems and data. For F5 BIG-IP, immediate patching is necessary. Security teams should audit systems for specific indicators of compromise, such as the presence of `/run/bigtlog.pipe` or `/run/bigstart.ltm`. We recommend verifying the integrity of system binaries like `/usr/bin/umount` and `/usr/sbin/httpd`, as unauthorized modifications to these files have occurred in recent campaigns.

When addressing a DeepLoad infection, standard file removal is insufficient. Organizations must specifically audit and remove unauthorized WMI event subscriptions to prevent recurrence. Because the software captures credentials from the moment of execution—including live keystrokes and session tokens—remediation must include a comprehensive password reset and session revocation for all accounts associated with the affected host. To detect the obfuscated PowerShell loaders, teams should enable PowerShell Script Block Logging and prioritize behavioral monitoring over static file scanning.

The use of AI to generate tailored obfuscation indicates that environmental noise will become harder to distinguish from legitimate code. As unauthorized parties shift toward less-monitored Windows features like WMI and specialized processes like `LockAppHost.exe`, defensive strategies must center on behavioral anomalies rather than static indicators. The reported Telegram vulnerability also serves as a reminder that zero-click vectors in messaging applications remain a high-value focus for capable actors targeting individuals with strategic communication needs.

While the server-side mitigations described by Telegram have reduced the immediate severity of the sticker-based issue, the underlying discrepancy between vendor statements and researcher findings leaves a gap in current knowledge. Until the full disclosure in July, users with high-stakes privacy needs should consider utilizing the web version of the application in a sandboxed browser or restricting message reception to trusted contacts.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Analyzing the Shift Toward Evasive Targeting in Core Infrastructure and Mobile Environments</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/315c3f74-cbc6-4b00-b96d-021e23228ec6</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/315c3f74-cbc6-4b00-b96d-021e23228ec6</guid>
        <pubDate>Sat, 28 Mar 2026 03:14:15 GMT</pubDate>
        <description>Recent data indicates that high-tier vulnerability frameworks are increasingly being adopted by broader threat groups to target telecommunications and OT environments. This report details the shift toward kernel-level evasion and provides proactive remediation strategies for network monitoring and post-quantum cryptographic agility.</description>
        <content:encoded><![CDATA[
            Over the last 24 hours, the threat situation has shifted toward more sophisticated and stealthy targeting of core infrastructure, ranging from the deep kernels of telecommunications backbones to the mobile devices and industrial systems that support global operations. Today’s developments indicate a concerning trend: high-tier, state-aligned methodologies are increasingly transitioning to opportunistic and financially motivated groups, making enterprise-grade security a moving target. For defensive teams, the perimeter extends well beyond the firewall; it now includes the kernel, the mobile keychain, and the encrypted packet itself.

One significant evolution in evasion comes from the threat group Red Menshen, also known as Earth Bluecrow. Researchers today revealed that the group has refined its BPFdoor Linux kernel module to better evade detection within telecommunications and critical infrastructure networks. Unlike traditional unauthorized software that creates high-volume network noise, BPFdoor operates passively within the Linux kernel, using the Berkeley Packet Filter (BPF) to watch for specific activation criteria. Recent reports show the group has moved away including broad packet monitoring and strictly hiding its triggers within standard HTTPS and ICMP traffic. By specifically monitoring the 26th byte offset of incoming TLS-encrypted requests, the unauthorized module remains dormant until it identifies a specific value, making it highly evasive to standard traffic inspection tools that categorize the data as benign.

This trend toward high-end evasion is mirrored in the mobile space. Sophisticated iOS vulnerability frameworks like Coruna and DarkSword have moved from the exclusive domain of state-level espionage to broader threat groups. Coruna, which is technically linked to the 2023 "Operation Triangulation" campaign, and DarkSword, whose components were recently published on GitHub, are now utilized by financially motivated groups and Russian-aligned actors like UNC6353. These frameworks are being modified with modules for cryptocurrency theft and credential harvesting. This proliferation means advanced capabilities once reserved for high-value diplomatic targets are now deployed in watering hole campaigns against retail and industrial vendors, lowering the barrier to entry for compromising the modern mobile workforce.

While software-based risks evolve, the physical domain remains under constant pressure. In the Middle East, internet-connected cameras have become strategic intelligence assets. Recent reporting shows a definitive shift in how unauthorized access to IP cameras is leveraged—moving away from botnet recruitment toward operational visibility and reconnaissance. In recent geopolitical events, access to traffic camera networks provided critical intelligence prior to kinetic operations. Following these events, scanning activity against camera networks in Israel and surrounding Gulf nations has spiked. For organizations in sensitive regions, an unpatched or exposed camera is a potential reconnaissance point that requires immediate remediation.

In the industrial sector, the overall volume of physically impactful operational technology (OT) security incidents saw a notable 25% decline in 2025. This marks the first reduction in seven years, likely driven by a temporary stabilization in the ransomware ecosystem and increased law enforcement pressure on major groups. However, defenders should remain vigilant. While physically disruptive events dropped to 57 recorded incidents, the targeting of critical infrastructure without immediate physical disruption doubled over the same period. High-profile cases, such as the security incident at Jaguar Land Rover that resulted in billions of dollars in economic impact, show that even a year with lower overall volume can still produce severe financial and operational consequences.

For security teams tasked with defending these environments, priorities should expand to include proactive, kernel-level telemetry and cryptographic resilience. Detecting BPFdoor requires monitoring for unauthorized BPF filters attached to network interfaces and restricting unnecessary ICMP communication between internal servers. Red Menshen frequently leverages the ICMP value `0xFFFFFFFF` to route commands between affected machines; we recommend integrating this pattern into internal traffic monitoring. On the mobile front, frameworks like Coruna can extract entire keychains and credentials in minutes. Relying solely on the native security of mobile operating systems is insufficient. Organizations need visibility platforms capable of detecting the anomalous behavior of these complex vulnerability frameworks before lateral movement begins.

As we build longer-term resilience, Google’s commitment today to a 2029 post-quantum cryptography (PQC) timeline provides a clear roadmap for the industry. Protecting authentication services and digital signatures is a critical defensive pivot. While the risk of "store-now-decrypt-later" exists for encrypted data, the risk to digital signatures requires transition before a cryptographically relevant quantum computer is realized. Security teams can begin this path today by conducting cryptographic inventories and ensuring that new deployments prioritize crypto agility, allowing for the seamless swapping of algorithms as NIST standards are finalized.

The convergence of state-level tools with malicious intent suggests a future where high-complexity methodologies are standard practice. Threat actors are tailoring BPFdoor to mimic legitimate HPE ProLiant and Kubernetes services, showing an intimate understanding of modern data center architecture. Defenders can match this knowledge by working closely with infrastructure teams to ensure kernel-level telemetry is captured and analyzed.

Gaps remain in our understanding of how these high-end tools are traded on the secondary market—specifically whether brokers or the actors themselves are adding new financial theft modules to kits like Coruna. Additionally, while the decline in OT incidents is a positive metric, a lack of transparency in reporting and potential legal liabilities suggest the true number of physical disruptions may be higher than public data indicates.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>The Proliferation of Advanced iOS Vulnerability Frameworks: Coruna and DarkSword</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/855e8b96-64de-4084-8030-6cf9dffaed49</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/855e8b96-64de-4084-8030-6cf9dffaed49</guid>
        <pubDate>Sat, 28 Mar 2026 03:14:15 GMT</pubDate>
        <description>Two sophisticated iOS vulnerability frameworks, Coruna and DarkSword, have transitioned including highly resourced origins to financially motivated threat actors. This shift emphasizes the need for organizations to implement comprehensive mobile visibility and credential protection and defend against advanced lateral movement capabilities.</description>
        <content:encoded><![CDATA[
            Coruna, an advanced mobile vulnerability framework utilizing zero-day vulnerabilities for high-level espionage operations, shares technical links with the 2023 Operation Triangulation surveillance campaign. Recent analysis shows that Coruna, along with a similar framework known as DarkSword, has transitioned into the hands of financially motivated groups and a Russian state-aligned actor tracked as UNC6353.

Furthermore, components of DarkSword were recently published to GitHub. This release significantly lowers the barrier to entry, placing advanced iOS compromise capabilities within reach of a broader range of unauthorized actors and requiring organizations to evaluate their mobile defense posture.

Rocky Cole, co-founder of iVerify—which analyzed both frameworks—indicates that the technology underlying Coruna was likely developed by Trenchant, the surveillance tech division of US military contractor L3Harris. Meanwhile, DarkSword, a separate tool with a comparable operational history, was likely developed in the Gulf region, potentially by the DarkMatter Group or former personnel.

"In the case of Coruna, it was very likely a government contractor who sold it to zero-day brokers," Cole notes. "In the case of DarkSword, I think it's possible the firm that developed it went defunct and offloaded it to try to salvage some investment. Either way, it made its way onto the secondary market for resale, and then from there fell into the hands of Russian state operators."

UNC6353 has deployed both tools via watering hole campaigns in Ukraine. These operations focused on commercial targets, including industrial and retail vendors, as well as local services and a news agency in the Donbas region. Researchers note that DarkSword has also been utilized by multiple commercial surveillance companies and suspected state-sponsored actors across Saudi Arabia, Turkey, Malaysia, and Ukraine. Following the GitHub publication, broader experimentation by unauthorized users has been observed.

## Technical Links to Operation Triangulation

In early 2023, Kaspersky identified anomalous behavior during routine security monitoring. The activity was identified internally on the company's own employees' devices.

This discovery provided the first evidence of Operation Triangulation, a four-year surveillance campaign affecting thousands of devices in Russia, including those of senior Kaspersky personnel and diplomatic missions. Russia's Federal Security Service (FSB) attributed the activity to the US National Security Agency (NSA).

Subsequent analysis by iVerify researchers revealed clear structural overlaps between the software used in Operation Triangulation and the newly discovered Coruna iOS framework. Following further technical review, Kaspersky confirmed that Coruna functions as an evolution of Operation Triangulation. The framework has since incorporated four new iOS kernel vulnerabilities, establishing a total of five vulnerability chains spanning 23 distinct CVEs.

Threat actors have actively customized this core architecture with varying delivery mechanisms and final modules tailored to specific operational objectives.

"The big difference between kits like Coruna and DarkSword and other top-tier iOS spyware is that both of the former tools had additional code added to them by an unknown party to introduce financial theft and cryptocurrency capabilities," explains Justin Albrecht, principal researcher at Lookout.

For example, while Coruna was originally deployed against highly specific targets, Google Threat Intelligence observed UNC6353 embedding it within invisible iframes on compromised Ukrainian websites. Additionally, a Chinese threat group tracked as UNC6691 removed the framework's geolocation restrictions to distribute it across cryptocurrency scam sites. UNC6691's deployment featured custom modules designed specifically for cryptocurrency theft, marking a significant departure from Coruna's original espionage focus.

Google researchers noted: "It’s not known whether the additional code was accomplished by the second-hand broker, or by the threat actors themselves, but we consider it highly likely that both Coruna and DarkSword were acquired and then modified to conduct financial theft as well as espionage."

## State-Level Capabilities Reach Financially Motivated Actors

Coruna is not the first advanced cyber capability to transition into Russian possession, and DarkSword represents the latest in a series of commercial surveillance tools utilized by non-state actors. However, the current environment demonstrates these tools migrating further down the resource chain to financially motivated groups.

Albrecht notes that the transfer of capabilities between state intelligence apparatuses and criminal organizations aligns with documented operational models. "We should consider Russia’s well documented use of criminal proxy groups to target Ukraine and to conduct financial theft," he says. "The relationship between Russian Intelligence organizations and various Russian cybercriminal groups, such as a partnership between RomCom and Trickbot, essentially functions as a modern-day privateer model."

This dynamic results in lower-tier threat actors operating with state-level technical capabilities. As Cole observes, "Coruna has 23 vulnerabilities across five chains. It probably costs $30 million to $40 million to develop something like that," a development cost far exceeding typical non-government malware.

## Defending Against Advanced Mobile Threats

As premium surveillance capabilities continue to proliferate to financially motivated threat actors, organizations that previously considered themselves outside the scope of advanced persistent threats (APTs) must update their defensive models.

Albrecht advises security leaders to prioritize advanced mobile protections and visibility platforms. "Consider that malware like this pulls entire keychains and credentials off of the device in minutes," he says. "At this point the risk isn’t only to the mobile device itself, because the attacker now has credentials and can merely log in to the corporate network. They have all Wi-Fi credentials, so their level of access and potential for lateral movement is elevated. Without visibility and protection on the iOS devices there’s no protection beyond what the OS provides to stop these attacks, and there’s certainly no visibility to know how and where the attack started."

Cole reinforces this assessment, noting that while Apple has patched the specific vulnerabilities utilized by these frameworks...
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Preparing for Google&apos;s 2029 post-quantum cryptography timeline</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/67f1e0ab-9cdc-48da-b354-e732a1cda69d</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/67f1e0ab-9cdc-48da-b354-e732a1cda69d</guid>
        <pubDate>Sat, 28 Mar 2026 03:14:15 GMT</pubDate>
        <description>Google has committed to integrating post-quantum cryptography (PQC) across its infrastructure by the end of 2029, with a specific focus on protecting authentication services. Security teams can begin preparing today by conducting cryptographic inventories, building crypto agility, and confirming vendor migration roadmaps.</description>
        <content:encoded><![CDATA[
            Google has established a timeline to integrate post-quantum cryptography (PQC) across its systems, products, and services by the end of 2029. Detailed in a recent announcement by Heather Adkins, vice president of security engineering, and Sophie Schmieg, senior staff cryptography engineer at Google, the migration aims to safeguard digital infrastructure against the evolving capabilities of quantum computation.

While quantum computers promise significant advancements in science, they also introduce risks to current authentication and encryption methodologies. As this technology becomes more accessible, unauthorized parties may use it to bypass existing security controls. To protect users and data, organizations like Google, Apple, and various public sector entities are prioritizing cryptographic algorithms designed to resist quantum computation. This transition is guided by the National Institute of Standards and Technology (NIST), which published its first finalized PQC standards in 2024.

## Google's post-quantum migration strategy

Google’s transition focuses on safely migrating to a post-quantum state within NIST’s current guidelines. The company has already begun rolling out PQC within its internal operations and products, centering its efforts on three areas: maintaining crypto agility, securing critical shared infrastructure, and supporting ecosystem-wide shifts to create a more resilient long-term security architecture.

A key detail in Google's updated threat model is the specific prioritization of authentication services. While encryption faces immediate exposure from "store-now-decrypt-later" data collection—where unauthorized parties gather encrypted data today to decrypt it once quantum technology matures—digital signatures represent a future risk that requires a transition to PQC before a Cryptographically Relevant Quantum Computer (CRQC) is developed. Google recommends that engineering teams prioritize PQC migration for authentication services to protect digital signatures and online security.

Supporting this 2029 commitment, Android 17 will integrate PQC digital signature protection using the Module-Lattice-Based Digital Signature Algorithm (ML-DSA). This addition expands upon previously announced post-quantum support within Google Chrome and Google Cloud.

## Preparing systems for the quantum transition

Security experts emphasize that a 2029 timeline is manageable and represents a proactive security posture. Melina Scotto, a cybersecurity executive adviser and chief information security officer, notes that while not every organization has Google's resources, engineering teams can prioritize intermediate protective measures, such as implementing strong salting techniques. Adding this layer of randomness to cryptographic processes increases the effort, cost, and time required for unauthorized parties to compromise data using precomputed methods, providing valuable interim protection while comprehensive encryption solutions are finalized.

Dustin Moody from NIST advises that falling behind on quantum preparation introduces broader risks, including future interoperability issues with partners who prioritize PQC. For organizations beginning this process, Moody recommends focusing on methodical preparedness rather than urgency.

Teams can strengthen their posture by taking the following steps:

* Conduct a cryptographic inventory: Build awareness by identifying exactly where and how cryptography is currently used within the environment.

* Engage service providers: Since many organizations rely on third-party solutions, engage with cloud platforms, VPN vendors, and software partners to confirm their specific post-quantum migration plans.

* Design for crypto agility: Ensure systems are built to adapt as cryptographic standards evolve over time.

* Protect sensitive data: Assign the highest priority to systems that protect long-lived sensitive data requiring confidentiality well into the future.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Operational Technology Security Incidents With Physical Consequences Decline by 25%</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/aafdbfce-f042-4cfa-87e7-18a65b34a2f9</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/aafdbfce-f042-4cfa-87e7-18a65b34a2f9</guid>
        <pubDate>Sat, 28 Mar 2026 03:14:14 GMT</pubDate>
        <description>A recent report indicates a 25% drop in physically impactful OT security incidents in 2025. We review the data, the underlying factors driving this change, and why event severity remains high despite the lower overall volume.</description>
        <content:encoded><![CDATA[
            The volume of major operational technology (OT) security incidents declined in 2025, marking the first reduction in seven years. Security metrics rarely show a downward trend without significant changes in the scene, making this anomaly an important data point for evaluating industrial defense strategies.

Historically, the number of OT incidents resulting in physical consequences for affected organizations has consistently grown, rising from a few isolated events prior to 2019 to 76 recorded incidents in 2024. According to the newly published annual report from Waterfall Security Solutions, 2025 deviated from this pattern. The organization identified 57 physically impactful OT incidents over the year. A 25% decrease that brings the total below both 2024 and 2023 levels.

Understanding the drivers behind this shift helps security teams anticipate future trends and focus their resources effectively.

## Factors influencing the decline

Researchers propose three primary hypotheses for the reduction in public OT incidents last year.

The first suggests that improved security practices are successfully protecting critical systems and giving defenders an edge. While difficult to measure comprehensively, this theory contrasts with the nature of some incidents that still occurred. For example, in January 2025, an unauthorized individual in Italy gained access to a system that allowed them to alter the routes of oil tankers and transport ships in the Mediterranean Sea. Andrew Ginter, vice president of industrial security at Waterfall Security Solutions, notes that threat actors frequently access exposed human-machine interfaces (HMIs) using default or compromised credentials. As a foundational protective measure, he strongly recommends that organizations ensure all HMIs are removed from the public internet.

A second hypothesis points to a decrease in public reporting. While many jurisdictions have implemented stricter disclosure regulations in recent years, these rules do not universally apply to all regions experiencing frequent OT incidents. Furthermore, aggregated reporting in sectors like European critical infrastructure often anonymizes the data before it reaches the public. Legal liabilities also play a role. Following cases where organizations faced legal action over initial incident disclosures—such as Marquis initiating a lawsuit against its firewall vendor SonicWall in early 2025 for allegedly underestimating an incident's impact, legal counsel frequently advises companies to limit public details strictly to what the law mandates.

The most prominent theory links the decline to a temporary reduction in ransomware events, which drove the majority of major OT incidents in the early 2020s. Law enforcement actions in the United States and Russia recently disrupted the incentive structures and operations of major ransomware groups, providing a temporary reprieve for OT environments. However, Ginter anticipates that this ecosystem is stabilizing. As new entities step in to provide the necessary technical infrastructure, organizations should prepare for activity to normalize in 2026.

## Technical complexity and event severity

Beyond frequency, the technical complexity of public OT incidents in 2025 was generally lower than in previous years. While 2024 saw the discovery of multiple new OT-specific malware strains—demonstrating a capacity to write custom code to implement protocols for programmable logic controllers (PLCs) and remote terminal units, 2025 lacked similar novel developments. Threat actors primarily relied on established methods and general IT-focused tools rather than specialized industrial protocols.

Exceptions to this lower technical complexity were observed in geopolitical contexts, such as the ongoing Russia-Ukraine conflict. Additionally, unconfirmed reports suggested sophisticated knowledge of anti-aircraft systems was leveraged against facilities in Iran and Venezuela in 2025, though reliable public details remain limited.

Despite the drop in volume and technical novelty, the severity of the incidents that did occur remained high. The security event affecting Jaguar Land Rover, for instance, resulted in an estimated $1 billion in direct losses and a $2.5 billion impact on the broader United Kingdom economy.

Additionally, politically motivated threat actors demonstrated continued interest in critical infrastructure. In one instance, unauthorized parties gained widespread access to Poland's solar and wind infrastructure. While they rendered an undisclosed number of automation devices inoperable, the event did not ultimately disrupt power delivery.

Overall, while incidents with physical consequences dropped 25%, the report found that targeting of critical infrastructure without physical disruption doubled over the same period. The data indicates that while the total number of physical disruptions decreased last year, the underlying risk to operational technology remains significant, requiring sustained, proactive defense.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Nation-state actors increasingly target exposed IP cameras for intelligence and physical targeting</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/ac3fa6da-1e3a-4848-a2be-697ea295255b</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/ac3fa6da-1e3a-4848-a2be-697ea295255b</guid>
        <pubDate>Sat, 28 Mar 2026 03:14:14 GMT</pubDate>
        <description>Recent geopolitical conflicts have driven threat actors to leverage compromised internet-connected cameras and cyber-physical systems for operational visibility. Security researchers emphasize that organizations must actively manage shadow IT and secure legacy IoT devices to avoid exposure in opportunistic scanning campaigns.</description>
        <content:encoded><![CDATA[
            Internet-connected cameras have shifted from being primary targets for botnet operators to strategic assets in geopolitical conflicts. Russian and Ukrainian forces have accessed cameras to gather intelligence, while a joint US-Israeli mission reportedly relied on connected cameras prior to a fatal strike on Iran's leader. Furthermore, Iranian actors have leveraged compromised devices for operational support and physical targeting.

Reports including the Financial Times and Associated Press indicate that Israel and the US accessed Iran's traffic camera network. Infrastructure the government used to monitor protesters—to track the movements of Ayatollah Ali Khamenei prior and a February 28 military strike. Following this event, Check Point Software reported that Iranian threat actors increased scanning and access attempts against camera networks in Israel, Qatar, Bahrain, Kuwait, the United Arab Emirates, and Cyprus.

This shift demonstrates that unauthorized access to IP cameras has evolved. Instead of merely co-opting devices for botnets, threat actors now prioritize intelligence gathering. Noam Moshe, a lead vulnerability researcher with cyber-physical security firm Claroty, notes a definitive transition toward controlling these devices for military, intelligence, and political purposes.

Sergey Shykevich, threat intelligence group manager at Check Point Research, explains that unauthorized camera access provides threat actors with direct visibility into targeted regions. He advises that leaving cameras unpatched or using default manufacturing credentials remains a primary security gap that organizations must close.

## Operational visibility through exposed devices

Historically, unauthorized access to cyber-physical systems was viewed as a serious but somewhat theoretical concern, with notable exceptions like the Stuxnet incident and the early stages of the Ukraine conflict. Today, accessing IP cameras to aid targeting and conduct battle damage assessment offers concrete, immediate value to nation-states.

As regional conflicts persist, Iranian-affiliated actors have broadened their scope to include private sector targets and industrial control systems, such as supervisory control and data acquisition (SCADA) systems and programmable logic controllers (PLCs), according to Moshe. Rather than strictly targeting specific organizations, these proxy groups conduct opportunistic scanning for exposed cyber-physical devices affiliated with particular countries. Organizations may find themselves caught in the geopolitical crossfire simply because their assets are externally exposed.

Security improvements by camera and Internet of Things (IoT) manufacturers have reduced the prevalence of easily accessible enterprise devices. Silas Cutler, a principal security researcher at Censys, points out that enterprise deployments are typically secured within private networks. The most frequently exposed hardware tends to be self-managed consumer devices.

## Securing legacy and shadow infrastructure

Legacy devices inadvertently connected to the public internet remain a primary source of exposure. Additionally, public benefit access to municipal traffic cameras can introduce security risks. Cutler recommends that organizations actively inventory their networks for shadow IT and outdated technology connected to the public internet.

When an unauthorized party discovers an exposed camera, they still need time to analyze the feed and determine its operational value. Moshe, who presented research on four vulnerabilities in Axis cameras at the Black Hat USA conference, explains that this analysis phase provides organizations with a window to detect and mitigate the exposure before the feed can be used effectively.

Maintaining defense in depth remains the most reliable strategy for protecting enterprise environments. Shykevich recommends that organizations regularly scan their own IP ranges to identify unprotected devices and apply missing patches. Establishing strong security hygiene, such as enforcing sturdy password policies and placing IoT devices behind firewalls with intrusion prevention capabilities—creates a resilient barrier against opportunistic scanning.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Red Menshen evolves BPFdoor implant to maintain covert access in global telecommunications</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/f23b8e7e-785f-4f6e-a28a-89fcfd0b32f9</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/f23b8e7e-785f-4f6e-a28a-89fcfd0b32f9</guid>
        <pubDate>Sat, 28 Mar 2026 03:14:14 GMT</pubDate>
        <description>The advanced persistent threat group Red Menshen has upgraded its BPFdoor Linux kernel implant to better evade detection within telecommunications, government, and critical infrastructure networks. By hiding triggers in standard HTTPS and ICMP traffic, the malware presents new visibility challenges that require security teams to adopt proactive, kernel-level threat hunting.</description>
        <content:encoded><![CDATA[
            Threat actors operating under the Red Menshen designation (also tracked as Earth Bluecrow) have modified the BPFdoor malware to maintain highly stealthy persistence within global telecommunications systems, government networks, and critical infrastructure.

BPFdoor operates within the Linux kernel. It passively uses the Berkeley Packet Filter (BPF) to inspect incoming network traffic for a specific activation message, remaining dormant and difficult to observe until triggered. Researchers at Rapid7 report that Red Menshen has recently refined this listening mechanism. Since late last year, the group has implemented additional evasion techniques to remain undetected while operating near the core of global telecommunications subscriber traffic.

While earlier telemetry identified affected organizations in the Middle East and Africa, Rapid7's Christiaan Beek confirms that the campaign is global, with established persistence in the Asia-Pacific (APAC) region and Europe. Originally focused on telecommunications, the threat actor has also expanded its targeting to include government, critical infrastructure, and defense networks.

## Evolution of a sophisticated telecommunications backdoor

Previously, BPFdoor monitored a wide range of network packets for its activation sequence. The updated implant now strictly looks for its trigger within standard Hypertext Transfer Protocol Secure (HTTPS) requests. By hiding the activation sequence within Transport Layer Security (TLS) traffic, the malware easily passes through standard firewalls and traffic inspection tools. Once decrypted, the request appears benign to human analysts and automated security solutions.

BPFdoor specifically monitors the 26th byte offset in the incoming request; if the trigger value appears at this exact location, the implant activates. Trend Micro's analysis of a recent BPFdoor controller reveals that the threat actor also uses a hard-coded password and salt, verifying the MD5 hash before allowing the reverse shell to open. The controller supports TCP and ICMP protocols, allowing the operators to adapt their connection methods based on the specific network restrictions of the affected organization.

Red Menshen also exercises precise control over multiple compromised servers within a single environment using a lightweight Internet Control Message Protocol (ICMP) channel. Rather than relying on traditional, easily detectable command-and-control (C2) servers for internal lateral movement, the malware transmits instructions between infected machines using ICMP pings. A specific value—`0xFFFFFFFF`—tells a specific machine to execute the enclosed command and terminate the propagation. Beek notes that this allows the threat actor to route commands through multiple network hops to a specific target machine, blending seamlessly into routine network diagnostic traffic.

## Deep reconnaissance and process masquerading

Red Menshen demonstrates an exceptional understanding of telecommunications infrastructure. Rapid7 observed the group performing extensive reconnaissance to understand the interconnections of specific equipment inside target networks. This deep operational knowledge allows them to move swiftly and deploy custom tooling, such as localized credential sniffers, once they establish a foothold.

The threat actor adapts its implants to mimic the specific environments of its targets. Knowing that many European and Asian telecommunications providers rely on HPE ProLiant servers and increasingly use Kubernetes to manage 5G core networks, BPFdoor actively disguises itself using legitimate service names and process behaviors associated with these specific technologies.

## Proactive hunting and defense strategies

BPFdoor’s combination of passive kernel-level listening, covert ICMP messaging, and highly tailored process masquerading makes it difficult for standard endpoint security solutions to detect. Protecting these environments requires security teams to actively hunt for anomalous internal traffic patterns.

To safeguard critical infrastructure, organizations should expand defensive visibility beyond the traditional perimeter. This includes monitoring high-port network activity on Linux systems, restricting unnecessary ICMP communication between internal servers, and hunting for unauthorized BPF filters attached to network interfaces. Triage recommends working closely with infrastructure teams to ensure that logging captures the specific kernel-level telemetry needed to identify this class of persistent threat. Telecommunications providers and critical infrastructure operators must anticipate these sophisticated techniques and validate their defensive posture continuously to maintain trust and operational resilience.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Accelerated Threat Timelines: Managing Risks in AI Frameworks and Global Supply Chains</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/1632b9c8-5e82-42ca-8b78-fb895d53ac56</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/1632b9c8-5e82-42ca-8b78-fb895d53ac56</guid>
        <pubDate>Fri, 27 Mar 2026 03:14:07 GMT</pubDate>
        <description>Recent vulnerabilities in AI frameworks and regulatory shifts in hardware procurement demonstrate a shrinking window for defensive response. This report outlines active risks across software and physical supply chains, providing actionable mitigations to help security teams maintain resilient, verified environments.</description>
        <content:encoded><![CDATA[
            The security scene today is defined by a shrinking window for defensive response, demonstrated by the rapid operationalization of a critical vulnerability in the Langflow AI framework. This development coincides with significant shifts in how national regulators and researchers view hardware and software supply chains, from the FCC’s restrictive new stance on foreign-made routers to fresh data showing that AI-assisted coding tools inadvertently introduce technical debt and vulnerabilities into enterprise environments. For security teams, the current operational environment shows that the pace of unauthorized access is accelerating. The tools organizations rely on for innovation, whether AI platforms or global hardware—require more rigorous operational oversight than ever before.

The most immediate risk involves CVE-2026-33017, a critical code injection vulnerability in Langflow, an open-source framework used to build AI agents. Within 24 hours of its disclosure, security researchers observed active scanning and unauthorized access attempts. This rapid turnaround prompted the Cybersecurity and Infrastructure Security Agency (CISA) to add the flaw to its Known Exploited Vulnerabilities catalog on Wednesday. The speed with which threat actors transitioned including a technical advisory to functional execution indicates a maturing capability; unauthorized parties were able and construct execution sequences even without a public proof-of-concept input. This serves as a clear indicator that the gap between disclosure and potential exposure is now measured in hours, particularly for high-value AI workloads that frequently manage sensitive API keys and cloud credentials.

Volatility in the AI ecosystem extends beyond direct unauthorized utilization of the platforms themselves. New research released today by Sonatype suggests that organizations using advanced large language models like GPT-5 and Claude 4.5 to manage software dependencies may be operating under a false sense of security. An analysis of over 250,000 AI-generated upgrade recommendations found that nearly 28% of dependency upgrades were hallucinations, non-existent versions or fixes that provide no security value. Equally concerning is the tendency for these models to suggest "no change" when faced with uncertainty, effectively leaving hundreds of critical vulnerabilities unpatched in production code. The data shows that while AI reasoning capabilities are advancing, the models lack the real-time ecosystem intelligence needed to make safe remediation decisions, occasionally recommending versions that introduce more risk into the software supply chain.

As software supply chains face AI-driven instability, the physical infrastructure of the network is undergoing a regulatory shift. The Federal Communications Commission recently moved to halt approvals for specific foreign-made routers, effective March 23, citing unacceptable national security risks. The directive, influenced by findings related to threat groups like Volt Typhoon and Salt Typhoon, aims to prevent unauthorized parties from introducing access mechanisms or conducting large-scale data collection through consumer and small-office equipment. However, industry researchers warn of a potential side effect: the creation of a "zombie hardware" problem. If the market for new, approved devices becomes more constrained or expensive, small businesses and organizations may retain older, out-of-support routers far beyond their intended lifecycle, creating a different but equally demanding set of security gaps.

These supply chain complexities are further obscured by an opaque market of intermediaries. A report from the Atlantic Council details how a global network of brokers, resellers, and contractors help the distribution of commercial surveillance technology, often bypassing international trade bans and transparency requirements. These third-party firms allow specialized intrusion capabilities to move into restricted markets by creating modular supply chains that hide the origin of the technology. For security teams, this means the tools used by sophisticated threat actors are increasingly decoupled from their original manufacturers, making "Know Your Vendor" requirements a critical, though difficult, component of modern risk management.

From a technical perspective, the Langflow vulnerability (CVE-2026-33017) affects a public build endpoint designed for convenience. The flaw resides in the way the application processes optional "data" parameters, passing Python code directly to the `exec()` function without sandboxing. This allows unauthenticated remote code execution. Because Langflow instances frequently store credentials for major cloud providers and AI services, a single instance of unauthorized access can help immediate lateral movement. We recommend security teams monitor for anomalous network callbacks or unexpected shell executions originating from AI development environments.

For software engineering teams, the Sonatype research provides a clear path for mitigation: "grounding." When AI models were paired with real-time intelligence—such as version recommendation APIs and developer trust scores, critical risks were reduced by nearly 70%. Security teams should verify that any AI-assisted development tools used by their engineering departments do not operate in a vacuum, but are instead integrated with live registry data and vulnerability intelligence. Relying on an ungrounded model to suggest a security patch currently presents an elevated risk, frequently resulting in either a hallucinated version or the preservation of a known vulnerability.

Regarding network infrastructure, the FCC’s policy shift indicates that hardware origin is becoming a primary security consideration for sovereign and high-security environments. However, teams must not let the focus on hardware manufacturing distract from operational fundamentals. Research shows that most router-related security incidents still stem from administrative oversight—default credentials, exposed management interfaces, and delayed firmware updates. Rather than built-in modifications. The most effective immediate defense is a return to basics: disabling remote management, enforcing strong credentials, and applying patches as soon as they are available, regardless of the device's country of origin.

Looking forward, the convergence of these trends demonstrates that standard verification models are struggling against rapid AI adoption and supply chain opacity. We are entering an era where software dependencies are suggested by hallucinating models and hardware is procured through complex webs of intermediaries. Success for defensive teams will increasingly depend on the ability to implement runtime detection and rigorous "Know Your Vendor" protocols. The incident with Langflow shows that organizations can no longer rely on a multi-day patching cycle for high-profile vulnerabilities; teams must have the visibility and segmentation in place to isolate affected workloads the moment an advisory is published.

As these developments progress, it remains to be seen how the FCC’s exemption process for new hardware will function or how quickly domestic manufacturing can fill the gap left by the new restrictions. Furthermore, while grounding AI models significantly reduces risk, the "human in the loop" remains a potential point of failure if reviewers rely on the same incomplete data as the models they oversee. Security teams should remain focused on bridging the gap between disclosure and remediation through automated response and live intelligence feeds.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Analyzing the Role of Intermediaries in the Commercial Surveillance Market</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/797f6f1d-8c52-43e7-a3d4-969978bec88c</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/797f6f1d-8c52-43e7-a3d4-969978bec88c</guid>
        <pubDate>Fri, 27 Mar 2026 03:14:07 GMT</pubDate>
        <description>The supply chain for commercial surveillance technology is growing increasingly complex due to a network of third-party intermediaries. A recent Atlantic Council report details how these brokers and resellers obscure visibility, complicating regulatory efforts while highlighting the need for stricter &quot;Know Your Vendor&quot; requirements.</description>
        <content:encoded><![CDATA[
            Understanding the commercial surveillance market has become increasingly complex due to the proliferation of intermediaries. These entities—including software resellers, vulnerability brokers, contractors, and regional partners—often enable government and private organizations to bypass transparency regulations and trade restrictions.

A March 18 report from the Atlantic Council details how these intermediaries allow the global distribution of offensive cyber capabilities (OCC). The researchers point to specific instances, such as a South African representative distributing Memento Labs' Dante software locally, and a third-party firm facilitating the sale of Passitora's surveillance technology to Bangladesh. This latter transaction occurred despite a lack of diplomatic relations between the relevant countries and existing trade bans, demonstrating how intermediaries navigate restricted markets.

Jen Roberts, associate director of the Cyber Statecraft Initiative at the Atlantic Council and a co-author of the report, notes that this ecosystem makes market analysis challenging.

"Intermediaries can drive down transparency efforts in the marketplace for offensive cyber capabilities like spyware by muddying supply chains and creating confusion for end buyers as to where a capability or component of a capability has come from," she says. She adds that intermediaries often support procurement for countries lacking strong in-house technical resources.

The broader commercial surveillance ecosystem continues to expand, driven by demand for law enforcement investigations, intelligence gathering, and the monitoring of political opposition. In 2025, a Google Threat Intelligence Group analysis found that, for the first time, commercial surveillance vendors accounted for more zero-day utilization than traditional state-sponsored groups. Recent shifts in US policy, including the reactivation of certain contracts and the removal of specific sanctions, also appear to have eased operational constraints for some surveillance technology vendors.

## The structural role of intermediaries

The Atlantic Council's "Mythical Beasts" report series indicates that intermediaries form the operational backbone of this market. By providing specialized procurement channels, they allow nations without domestic development capabilities to acquire gray-market surveillance software while insulating the original vendors from direct oversight.

Collin Hogue-Spears, senior director of solution management at Black Duck, explains that third-party brokers and resellers effectively bypass export controls through careful corporate structuring.

"Their corporate structures exist specifically to make export controls irrelevant," he notes. "The spyware market stopped being a vendor-to-government pipeline years ago. It has evolved into a modular supply chain where intermediaries fill every gap the buyer cannot fill alone: exploit engineering, operational training, deployment infrastructure, and most importantly, a legal paper trail that hides the origin."

Julian-Ferdinand Vögele, a principal threat researcher at Recorded Future, observes that these entities lower the barrier to entry by bundling software with training and support.

"Commercial spyware operates in the shadows by design," Vögele says. "Brokers and resellers enable its spread by connecting vendors and buyers, bundling tools with support or training, and expanding into new markets, while adding opacity, obscuring relationships, and leveraging jurisdictions."

## Regulatory efforts and transparency initiatives

Recognizing the risks to affected parties, including journalists, diplomats, and civil society members, international coalitions are working to establish oversight. In February 2024, the United Kingdom and France launched the Pall Mall Process, a multilateral initiative aimed at addressing the proliferation and irresponsible use of commercial cyber intrusion capabilities. This ongoing effort brings together government entities, industry partners, and policy experts to develop standard practices and safeguards.

In response to mounting regulatory pressure, some surveillance vendors have introduced internal compliance measures. For example, NSO Group announced the establishment of a human rights compliance program, though independent researchers remain cautious about the effectiveness of self-regulation in this sector.

Roberts notes that the Pall Mall Process is currently focused on drafting an industry code of practice, meaning comprehensive evaluation of the initiative will take time. In the interim, the Atlantic Council recommends practical defensive steps for organizations and governments: implementing strict "Know Your Vendor" requirements, mandating certification for capability brokers and resellers, and maintaining clear public registries of these entities.

Establishing visibility into the procurement chain is a necessary first step for security practitioners and policymakers attempting to secure environments against these tools.

"Transparency initiatives are key to regulating intermediaries and also the spyware industry more broadly," Roberts says. "It is difficult to ultimately regulate what one cannot observe."
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Evaluating AI models for software dependency decisions</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/e96f9a28-051e-424b-9813-85a7c8d6023a</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/e96f9a28-051e-424b-9813-85a7c8d6023a</guid>
        <pubDate>Fri, 27 Mar 2026 03:14:06 GMT</pubDate>
        <description>Recent analysis indicates that organizations relying on large language models for software dependency upgrades may inadvertently introduce or maintain vulnerabilities. Integrating real-time ecosystem intelligence is necessary to ensure AI-assisted development tools provide accurate, secure remediation guidance.</description>
        <content:encoded><![CDATA[
            Organizations integrating AI models into their software dependency workflows should evaluate how these tools source and verify their upgrade recommendations.

Recent research from Sonatype evaluated the performance of "frontier" models, the most advanced AI models available—when tasked with providing upgrade and patching guidance for software dependencies. The data shows that while these tools offer productivity benefits, they frequently generate fabricated or inaccurate recommendations, complicating vulnerability management and potentially increasing technical debt.

To measure this, Sonatype’s research team analyzed 36,870 unique dependency upgrade recommendations across Maven Central, npm, PyPI, and NuGet between June and August 2025. The study encompassed a total of 258,000 recommendations generated by seven AI models from Anthropic, OpenAI, and Google.

The initial phase of the study, published in February 2026 as part of the State of the Software Supply Chain report, focused on OpenAI's GPT-5. The analysis found that the model often recommended software versions, upgrade paths, or security fixes that did not exist, with nearly 28% of the recommended dependency upgrades classified as hallucinations.

A second phase of the study evaluated newer models equipped with enhanced reasoning capabilities, including GPT-5.2, Anthropic's Claude Sonnet 3.7 and 4.5, Claude Opus 4.6, and Google's Gemini 2.5 Pro and 3 Pro. While these models showed measurable improvements, they continued to generate a significant volume of fabricated recommendations. According to the report, these failures can lead to wasted AI spend, diverted developer time, unresolved vulnerability exposure, and increased technical debt before code reaches production.

## Evaluating recommendation accuracy

The research indicates that the primary limitation is not the reasoning capabilities of the models, which have advanced consistently. Instead, the models lack "ecosystem intelligence". The real-time dependency, vulnerability, compatibility, and enterprise policy context necessary to make safe remediation decisions.

Even the highest-performing models in the study fabricated approximately one out of every 16 dependency recommendations. To reduce hallucinations, frontier models often defaulted to a "no change" recommendation for about a third of the software components. However, this cautious approach resulted in the models failing to flag existing vulnerabilities. As a result, 800 and 900 critical and high-severity vulnerabilities were left unaddressed in production code during the evaluation.

In other instances, the models recommended software versions that contained known vulnerabilities. The report noted that this occasionally put the AI stack itself at elevated risk, as the libraries used to train, fine-tune, orchestrate, and serve the models were updated to vulnerable versions based on the models' own guidance.

Sonatype co-founder and CTO Brian Fox noted that inaccurate guidance from AI models creates a subtle accumulation of technical debt. While organizations generally expect AI models to make occasional errors, the research indicates that flaws in dependency recommendations are becoming quietly integrated into standard development workflows.

"The most dangerous version of this problem isn't when the model gives you something obviously broken," Fox said. "It's when it gives you something plausible that preserves risk, misses the better upgrade path, and looks close enough to ship."

## Grounding AI with real-time intelligence

The data provides a clear path forward for organizations using AI-assisted development. The study demonstrated that "grounding" AI models with live intelligence and context produces significantly safer outcomes. When comparing the ungrounded frontier models to a hybrid approach that applied real-time intelligence at inference time, the hybrid method yielded a nearly 70% reduction in critical and high risks.

To test this methodology, researchers equipped GPT-5 Nano—the smallest model in the GPT-5 family, with a single function-calling tool backed by a version recommendation API. Supplying the model with ranked upgrade candidates, vulnerability counts, and developer trust scores led to a marked reduction in vulnerabilities compared to the ungrounded frontier models.

The report found that grounding not only prevents hallucinations but also successfully steers the model toward component versions with fewer known vulnerabilities when a perfect upgrade path is unavailable.

Without live registry data, vulnerability intelligence, or compatibility context, AI models will continue to output errors that require engineering time to correct. Simply adding a human review step to the process is unlikely to prevent these issues if the reviewer is relying on the same incomplete data. As Fox explained, humans should set policies and constraints, but the systems providing recommendations must remain grounded in real-time software intelligence to support safe, effective decision-making.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Critical Vulnerability in Langflow AI Platform Requires Immediate Remediation</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/dca5435d-bee4-48df-b656-b4a7e2bef9cb</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/dca5435d-bee4-48df-b656-b4a7e2bef9cb</guid>
        <pubDate>Fri, 27 Mar 2026 03:14:06 GMT</pubDate>
        <description>A critical code injection flaw in the Langflow AI framework (CVE-2026-33017) allows unauthenticated remote code execution. With active scanning and unauthorized access attempts observed within 24 hours of disclosure, organizations must upgrade to version 1.9.0 and implement runtime defenses immediately.</description>
        <content:encoded><![CDATA[
            According to reporting from Dark Reading, a critical vulnerability in Langflow—an open-source framework for AI agent development—has been subject to active security incidents shortly after its initial disclosure.

On Wednesday, the Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-33017, a critical code injection flaw, to its Known Exploited Vulnerabilities (KEV) catalog. The vulnerability carries a 9.8 CVSS score and was first disclosed on March 17, 2026. Reports of unauthorized activity emerged almost immediately.

Cloud security vendor Sysdig observed access attempts less than 24 hours after the vulnerability was disclosed. Sysdig researchers noted that malicious actors were able to use the technical details provided in the advisory to quickly construct functional code execution sequences, even though no public proof-of-concept (PoC) code was initially available.

This rapid turnaround indicates that the window between vulnerability disclosure and active network scanning is now measured in hours, rather than days or weeks. Researchers noted that AI workloads are frequently targeted because they process high-value data and provide software supply chain access, often before comprehensive security measures are fully implemented.

## Technical details of CVE-2026-33017

Langflow is a widely used low-code framework for building and deploying AI agents. The vulnerability, CVE-2026-33017, originates in the `POST /api/v1/build_public_tmp/{flow_id}/flow` endpoint, which is designed to allow users to build public flows without authentication.

According to the Langflow GitHub advisory, if a user supplies the optional "data" parameter, the endpoint processes the provided flow data instead of the stored flow data from the local database. If this input contains arbitrary Python code within node definitions, the application passes the code directly to the `exec()` function without sandboxing. This mechanism grants unauthenticated remote code execution (RCE) to anyone who can reach the endpoint.

Langflow clarified that this issue is distinct from CVE-2025-3248, an earlier vulnerability that was previously utilized to distribute the Flodrix botnet.

The technical advisory for CVE-2026-33017 included specific details, such as the vulnerable endpoint path and the exact code injection mechanism. This transparency, while vital for defenders, provided enough information for unauthorized parties to formulate operational inputs without requiring extensive independent research.

## System impact and remediation

Researchers warn that unauthorized parties who successfully execute arbitrary code via CVE-2026-33017 can extract sensitive configuration data from vulnerable Langflow instances. Because these instances often store API keys and credentials for services like OpenAI, Anthropic, and AWS, exposure can enable lateral movement to connected databases and external cloud environments.

To protect your systems, we recommend the following immediate actions:

* Upgrade immediately: Langflow version 1.9.0 mitigates this vulnerability. System administrators should upgrade to the fixed version as soon as possible.

* Implement runtime detection: Utilize runtime security monitoring to identify unexpected shell execution or anomalous network callbacks originating from AI workloads.

* Segment networks: Isolate AI development frameworks from critical production databases and restrict outbound external access to only necessary, approved endpoints.

* Accelerate response capabilities: Organizations operating on scheduled, delayed patch cycles face an elevated risk during the critical hours following a disclosure. Bridging the gap between disclosure and remediation requires rapid, targeted response procedures.

Securing AI pipelines is a collaborative effort. By taking these steps, security and engineering teams can ensure their organizations continue building innovative applications safely and confidently.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Evaluating the Security Impact of the FCC&apos;s Router Ban</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/e3921f5e-a7e6-4627-b246-1acfe74e79d9</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/e3921f5e-a7e6-4627-b246-1acfe74e79d9</guid>
        <pubDate>Fri, 27 Mar 2026 03:14:06 GMT</pubDate>
        <description>The FCC&apos;s recent decision to halt approvals for specific foreign-made routers aims to protect national infrastructure, but industry researchers caution it could complicate hardware replacement cycles. Organizations can maintain strong defensive postures by focusing on operational security fundamentals while the hardware market adapts.</description>
        <content:encoded><![CDATA[
            The Federal Communications Commission (FCC) recently decided to add specific foreign-made routers to its national security risk list. While intended to protect infrastructure, this March 23 policy change introduces complexities that could inadvertently extend the lifecycle of older, less secure hardware for US consumers and small businesses over the long term.

The directive restricts the import of new consumer-grade router models manufactured outside the US. Organizations and consumers can continue using their current devices, and retailers may still sell previously approved models. However, the FCC will halt approvals for new foreign-made consumer routers, though it will review exemption requests as needed. The agency based this decision on findings from a White House-convened interagency body, which concluded that these devices present unacceptable national security risks.

## Assessing the national security context

The FCC documented concerns that unauthorized parties could introduce backdoors or tamper with routers to conduct mass surveillance, expose sensitive data, establish botnets, and gain unauthorized access to critical networks. According to the agency, security gaps in foreign-made routers have allow intellectual property theft and network disruption. They specifically referenced the Volt Typhoon, Flax Typhoon, and Salt Typhoon security incidents as examples of events involving foreign-made equipment.

Currently, the vast majority of small office/home office (SOHO) and commercial-grade routers used in the US are manufactured internationally. Rebecca Krauthamer, CEO and co-founder of QuSecure, notes that supply chain risks are genuine, particularly at the national security level. The FCC's restriction focuses on limiting geopolitical exposure and reliance on foreign-controlled components, extending beyond device-level vulnerabilities.

"We are seeing a broader shift toward sovereign and trusted technology stacks in higher-security environments," Krauthamer explains, noting that the origin of infrastructure components is a meaningful consideration when sensitive data is involved.

## Potential side effects on hardware lifecycles

The heavy reliance on imported routers introduces questions about whether the restriction might prompt users to hold onto older, out-of-support devices. Krauthamer observes that while the policy does not mandate immediate replacement, it complicates future procurement. Many businesses rely on routers that have been in place for a decade or more, sitting directly in the critical path of their network traffic. Upgrading this infrastructure could soon involve a more constrained, potentially more expensive market with longer procurement cycles.

Jim Needham, senior managing director at FTI Consulting, explains that businesses might retain outdated equipment well beyond normal replacement cycles, which can weaken overall security postures. Since most routers require periodic replacement to maintain current security standards and keep pace with hardware advancements, the restriction could increase costs and cause operational friction. Because the ruling is prospective, however, these concerns apply primarily to future planning.

## Prioritizing operational security fundamentals

Several security researchers point out that device vulnerabilities are rarely tied directly to manufacturing origin. Instead, risk typically stems from operational gaps, such as default credentials, delayed patch management, and exposed management interfaces.

Jason Soroko, senior fellow at Sectigo, notes that unauthorized parties leverage these vulnerabilities across both domestic and international hardware alike. He cautions against focusing solely on hardware origin rather than maintenance rigor, which could misdirect attention away from the more pervasive issue of administrative oversight.

For contrast, the European Union addresses device security through its Cyber Resilience Act. This legislation requires manufacturers selling connected devices in Europe to meet mandatory cybersecurity requirements. Including secure defaults, vulnerability disclosure, and ongoing software support—regardless of where the hardware was built.

## Navigating future equipment replacements

Currently, the FCC's restriction serves as a forward-looking measure. The practical impact will surface as existing equipment reaches end-of-life and organizations enter a constrained replacement market. Pieter Arntz, a researcher at Malwarebytes, observed only one US-made router, Starlink—currently available in the consumer category affected by the FCC's policy.

The core challenge for the industry is whether the lack of domestic alternatives will spur new investment in US manufacturing or result in prolonged use of aging hardware. The outcome will depend heavily on how the FCC manages its exemption process. In the meantime, security teams can best protect their environments by focusing on rigorous operational hygiene: applying firmware updates promptly, disabling unnecessary remote management interfaces, and strictly controlling administrative credentials.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
    <item>
        <title>Evolving Defense Methodologies and AI Automation at RSAC 2026</title>
        <link>https://shortwaveslive.vdp.triagesecurity.ai/blog/d4044e73-7f44-4f68-81f7-4c2aee40272e</link>
        <guid isPermaLink="true">https://shortwaveslive.vdp.triagesecurity.ai/blog/d4044e73-7f44-4f68-81f7-4c2aee40272e</guid>
        <pubDate>Thu, 26 Mar 2026 03:20:50 GMT</pubDate>
        <description>An analysis of security developments discussed at RSAC 2026, focusing on the acceleration of AI-driven threat methodologies and the necessary shift toward automated, human-validated defensive workflows. The findings emphasize the importance of verifiable software supply chains and deliberate attribution strategies.</description>
        <content:encoded><![CDATA[
            The RSAC 2026 Conference in San Francisco opened today with a notable shift in international cooperation and the dynamics of automated security operations. Following the withdrawal of U.S. federal agencies, including the FBI and NSA, a response to the conference appointing former CISA Director Jen Easterly as CEO—European cybersecurity leaders have assumed a more prominent role. This transition aligns with a critical period where the speed of unauthorized operations is beginning to surpass traditional, manual defense capabilities, driven largely by the broader availability of artificial intelligence.

Discussions this morning prioritized "vibe coding," a term Dr. Richard Horne of the UK’s National Cyber Security Centre used to describe rapid, AI-assisted software generation. While these tools offer an alternative to the historically vulnerable manual coding process, they simultaneously lower the barrier for generating new software that can propagate unintended vulnerabilities at scale. SANS researchers presented supporting data today indicating that AI now forms the foundation of modern threat methodologies. Malicious actors are utilizing AI models to identify zero-day vulnerabilities in production software for as little as $116 in token costs. This economic shift means advanced discovery techniques are no longer exclusive to well-funded nation-states.

## The acceleration of automated operations

The technical gap between unauthorized access methods and defensive response is widening. Current estimates indicate that AI-driven operations proceed approximately 47 times faster than manual processes. For example, campaigns attributed to the Chinese state-sponsored group GTG 1002 show reconnaissance and lateral movement running at 90% automation. Under these conditions, a compromised credential can result in full administrative control of a cloud environment in under ten minutes.

This acceleration requires organizations to reevaluate incident handling, particularly in operational technology (OT) environments where visibility is often limited. A recent energy sector disruption in Poland demonstrated that without comprehensive OT logging, investigators cannot reliably determine whether a facility failure resulted from a targeted cyber event or a mechanical issue.

Defenders are also managing reputational risks generated by politically motivated threat actors. Iran-aligned groups, including Nasir Security, have applied sophisticated public relations tactics to overstate their operational impact today. By targeting smaller engineering and construction contractors within the supply chain, these groups exfiltrate legitimate internal documents and present them as evidence of unauthorized access at major energy organizations like Dubai Petroleum. The material impact on the primary targets remains negligible, but the psychological effect creates uncertainty. Similarly, groups like the 313 Team use the ambiguity of denial-of-service claims to maintain visibility in the news cycle.

Alongside high-level geopolitical shifts, senior professionals face targeted recruitment fraud. Threat actors impersonating Palo Alto Networks recruiters have spent the last several months executing highly personalized LinkedIn-based social engineering campaigns against executives. The methodology involves manufacturing a bureaucratic hurdle, informing the candidate that their resume failed an automated applicant tracking system (ATS) check—and directing them to a "third-party expert" who charges up to $800 for resume optimization. This campaign leverages the complexity of modern hiring processes to extract fees, demonstrating that the human element remains a primary vector for manipulation even as technical threats become more automated.

## Implementing human-in-the-loop defense

For security teams, these developments necessitate a transition toward proactive, automated validation. In the software supply chain, relying on standard bills of materials (SBOMs) is no longer sufficient. Organizations need to request verifiable proof of how software is built and implement automated patching cycles to match the speed of AI-generated threat methodologies. Regarding AI-assisted defense, experts agreed today that while open-source tools like Protocol SIFT can compress a two-week investigation into 15 minutes, human analysts must remain the final decision makers. Current AI lacks the contextual awareness to reliably interpret evidence, and a confident but incorrect verdict including an AI tool can waste critical hours during an active security incident.

Strategic guidance on public attribution is also evolving. Panelists cautioned against attributing incidents and nation-states as a method of diverting responsibility. While identifying a sophisticated adversary might seem advantageous for public relations, it frequently extends the news cycle and introduces insurance complications, such as "act of war" exclusions. Legal experts advise maintaining a strict "investigation ongoing" stance rather than offering a "no comment." This approach helps the organization control the narrative without making probabilistic claims that could invite secondary actions from the threat actors.

Looking toward the implementation of the EU Cyber Resilience Act in late 2027, the gap between government policy and private sector implementation remains a point of friction. Former NSA directors noted today that the absence of a unified federal data privacy framework or major cyber legislation in the U.S. continues to complicate defensive synchronization. While the thresholds for kinetic military responses to cyber incidents remain at the discretion of the presidency, the day-to-day responsibility for defense rests on private organizations. These entities must secure their data, their supplier ecosystems, and the AI tools utilized to build their infrastructure.

Significant gaps remain in understanding how autonomous agents will interact within OT environments and the full vulnerability footprint of "vibe coding." However, adopting accelerated, human-in-the-loop defensive workflows provides a viable path forward in an environment where the speed of unauthorized operations is no longer limited by manual interaction.
        ]]></content:encoded>
        <author>Triage Security Media Team</author>
    </item>
</channel>
</rss>