Win32/Spy.Ranbyus targeted remote banking and payment software in Ukraine and Russia, with a particular focus on BIFIT’s iBank 2 platform used in Ukraine. The malware was designed to bypass transaction signing and authentication tied to smartcard devices, enabling attackers to interfere with payment workflows inside remote banking environments.
Rather than modifying the Java Virtual Machine, the trojan evolved to patch Java code within specific banking applications, helping it evade protections while manipulating transactions. Ranbyus also collected host information for command-and-control servers, used form-grabbing techniques to steal payment data, and falsified account balance information to conceal unauthorized transfers, with Ukraine reported as the most heavily affected region.

See the actors and campaigns active against you right now.
1 event from the most recent confirmed update back to the earliest known activity.
ESET reported that the Win32/Spy.Ranbyus banking trojan had evolved to modify Java code inside BIFIT's iBank 2 remote banking system in Ukraine, enabling theft from targeted banking and payment software while bypassing smartcard-based signing and authentication.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See the adversaries and campaigns active against your sector right now, ranked by what they're exploiting.
1 reference tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.