Cybersecurity researchers at Elastic Security Labs have uncovered a sophisticated and previously undocumented financial threat operation targeting users in Brazil. The campaign, designated REF9334, has been active since May 2025 and focuses on the deployment of a robust malware toolkit identified as KREMLIN. This operation distinguishes itself through its innovative use of blockchain technology to decentralize command-and-control (C2) infrastructure, rendering it exceptionally resilient against traditional takedown efforts. By masquerading as legitimate banking documents and invoices, the threat actors successfully compromise systems to install malicious browser extensions on Google Chrome and Microsoft Edge, effectively turning web browsers into tools for credential theft and session hijacking.
The Anatomy of the KREMLIN Toolkit
The KREMLIN ecosystem is a multi-layered threat designed for stealth and persistence. The infection chain begins with a seemingly innocuous JavaScript file, often distributed via phishing emails or malicious advertisements that mimic legitimate communication from major Brazilian financial institutions. When a user manually executes this file, it triggers a multi-stage loader. This loader is equipped with rigorous environment-awareness capabilities; it performs extensive checks to determine if it is running within a sandbox or a virtual machine. If the malware detects virtualization software or suspicious system artifacts—such as a low number of CPUs or limited RAM—it terminates immediately to avoid analysis.
The second stage of the infection is where the operation’s technical sophistication becomes apparent. Once the loader successfully confirms it is running on a genuine host machine, it establishes persistence via scheduled tasks. Crucially, the malware retrieves the locations of its next-stage payloads from an Ethereum smart contract. By using blockchain-based dead drop resolvers, the attackers can dynamically update their infrastructure without relying on static, easily blacklisted domains. This approach ensures that even if a security firm identifies one C2 server, the actors can pivot to new, decentralized endpoints almost instantaneously.

Evasion and Persistence Mechanisms
The malware utilizes a C++ installer that employs binary sideloading to bypass security protections. By abusing a legitimate, signed binary—specifically the SentinelOne agent—the attackers inject an unsigned malicious payload, which they have masked as "SentinelAgentCore.dll." This mimicry is designed to trick automated security tools that may trust the legitimate process.
Once the DLL is active, it initiates the deployment of a malicious browser extension, which the attackers have dubbed "AVSync System Inc." To install this extension on Chromium-based browsers without alerting the user or triggering browser integrity protections, the malware utilizes "Phantom Extension" and "GhostChrome-X" techniques. These methods involve modifying the browser’s "Secure Preferences" file and regenerating the required HMACs (Hash-based Message Authentication Codes) to deceive the browser into believing the extension was installed legitimately by the user.
This sophisticated technique allows the attackers to maintain a persistent foothold within the browser. Once installed, the extension requests broad permissions, including access to cookies, browser storage, and the webRequest API. This level of access grants the attackers the ability to harvest session tokens, login credentials, and other sensitive financial data, which are then exfiltrated to the attackers’ C2 server.
Chronology of the REF9334 Threat Actor
The evolution of the REF9334 group demonstrates a clear progression in technical capability and operational maturity. Since its inception in May 2025, the group has transitioned from simple, off-the-shelf Trojans to a highly customized, blockchain-enabled framework.

- May 2025: Initial activity of the REF9334 actor is observed, primarily utilizing common Trojans such as Pulsar RAT and Remcos RAT.
- June 16, 2025: The first of seven distinct, high-impact campaigns is recorded, signaling a shift toward more targeted phishing efforts.
- May 19, 2026: A critical turning point in the operation occurs as the threat actors integrate Ethereum smart contracts to manage their C2 infrastructure, effectively hiding their backend from law enforcement and security researchers.
- August 2026: The group adopts advanced "Phantom Extension" techniques, aligning their tactics with other sophisticated actors like the China-linked APT31, who were simultaneously using similar methods to distribute the GemStone extension.
- Late 2026 to Present: The campaign continues to focus heavily on the Brazilian market, with researchers identifying over 1,500 infected systems in a single network canary analysis.
Supporting Data and Statistical Analysis
The scale of the KREMLIN operation is evidenced by the telemetry data gathered by Elastic Security Labs. Through the registration of a network canary domain—a domain used by the malware to test for internet connectivity—researchers were able to track the reach of the infection. The analysis identified 1,515 distinct infected endpoints attempting to communicate with the canary domain.
The geographic distribution of these infections is heavily concentrated, with over 98% of the compromised systems located within Brazil. This localization suggests that the threat actors have tailored their social engineering lures, banking impersonations, and language-specific phishing content specifically for the Brazilian financial sector. The sheer volume of compromised endpoints underscores the effectiveness of their automated delivery system and the relative lack of awareness regarding "browser-in-the-browser" style attacks among regional users.
Implications for Enterprise Security
The emergence of the KREMLIN toolkit highlights a growing trend in cybercrime: the professionalization of malware distribution through decentralized infrastructure. By leveraging blockchain, threat actors have effectively solved one of their greatest operational challenges—infrastructure stability. Traditional defensive measures, such as IP blacklisting or domain sinkholing, are largely ineffective against a C2 structure that pulls updates directly from a public ledger.
Furthermore, the abuse of browser integrity mechanisms poses a significant challenge for endpoint detection and response (EDR) solutions. Browser extensions are frequently viewed by users and administrators as low-risk utilities. However, when combined with sophisticated integrity bypass techniques like those seen in the KREMLIN campaign, they become potent vectors for persistent espionage and financial theft.

The use of "network canary" checks as an anti-analysis mechanism also suggests a high level of sophistication among the developers of the KREMLIN malware. By checking for a specific response from a non-existent domain, the malware can detect when it is being monitored in a sandbox, as sandbox environments often resolve all DNS queries to prevent the malware from "calling home."
Defensive Recommendations and Future Outlook
Security researchers emphasize that defending against such advanced threats requires a multi-layered approach. Organizations should implement strict policies regarding browser extensions, potentially utilizing Group Policy or Mobile Device Management (MDM) to force-install only approved, enterprise-vetted extensions. Additionally, because the malware relies on manual execution of suspicious files, ongoing security awareness training remains a vital defense against the initial phishing lures.
The transition to blockchain-backed C2 infrastructure is a harbinger of a broader shift in the threat landscape. As cybercriminal groups continue to adopt decentralized technologies, defenders must move toward behavioral analysis that focuses on detecting the actions of the malware—such as unauthorized modifications to browser preference files—rather than relying solely on indicators of compromise (IoCs) like static IP addresses or domain names.
As the REF9334 actor continues to refine its toolkit, the cybersecurity community remains on high alert. The integration of zero-day exploits and advanced persistence techniques suggests that this group will likely remain a significant threat to financial institutions and their customers for the foreseeable future. The ability to manipulate browser security at the architectural level represents a significant evolution in the sophistication of banking Trojans, necessitating a proactive and adaptive stance from both cybersecurity vendors and the financial sector.
