PixelLeaks Claims MT5 Trading Farm in New Listing
The extortion group PixelLeaks has listed an algorithmic-trading farm running MetaTrader 5 as a victim on its leak site, according to threat intelligence reports published on 21 November. The claim is unverified, and no evidence of a breach has been published alongside it.
The listing was discovered at 22:54 UTC on 20 November, according to the ransomware.live tracker, and was reported by the ThreatMon Threat Intelligence Team on 21 November. It identifies the target as an MT5 algorithmic-trading farm associated with a OneFunded funded account and a Windows Server system. The operation is described in the leak-site record as an algorithmic-trading operation, an MT5 and Westernpips high-frequency-trading arbitrage farm.
What the listing says
The post describes the material as a verified set of records from the trading operation, comprising business records including client and operational material, and gives a publication deadline of 24 November 2026 at 22:22 UTC. It gives no ransom amount and no data volume, and it includes no screenshots or other images. It does not claim that systems were encrypted, and no sample of the claimed records has been published.
HookPhish, which also tracks the listing, records the same details and the same deadline. RedPacket Security, which scrapes the group’s leak page, likewise records the post as a claimed data disclosure with a 24 November publication date, and notes that it provides no compromise date, so 20 November is the post date rather than a confirmed date of intrusion.
That is the full extent of what is known. The listing does not establish that PixelLeaks obtained access to actual trading accounts, financial assets or customer information, and no verified data theft, financial damage or operational disruption has been established by the available reporting.
Why a trading farm is a tempting target
MetaTrader 5 is widely used for financial market trading, automated strategies, expert advisors and algorithmic execution. A trading farm typically involves infrastructure supporting multiple automated trading processes or trading accounts, so a genuine compromise could potentially expose automated trading configurations, expert advisors and algorithmic strategies, trading account credentials or session information, server-side configuration files, and connections to brokerage or trading services.
Exposure of trading credentials could create risks beyond conventional corporate data exposure, including the misuse of trading accounts. But none of that has been shown here: there is no confirmation that trading credentials were accessed, and no evidence that financial transactions were manipulated. The absence of published samples does not prove no compromise occurred, but a victim listing alone does not prove that the group holds stolen information either.
For trading operations watching this claim, the practical lessons do not depend on whether this particular listing proves true. Windows Server authentication logs and suspicious remote-access activity deserve review, trading credentials that may have been exposed should be rotated, and trading infrastructure should be isolated from unnecessary corporate network access. The next development to watch for is either a statement from the affected operation or the publication of evidence by the group. Until one of those appears, the trading farm remains an alleged victim, not a confirmed one.