Join our FREE personalized newsletter for news, trends, and insights that matter to everyone in America

Newsletter
New

Hackers Hijack Banking Servers Without Passwords Using Bankweaver Attack

Hackers gained administrative access to a financial services institution’s Temenos Quantum Fabric deployment without valid credentials in a campaign researchers named BankWeaver.

Investigators uncovered the breach in early September and found six other banks across Asia, the Middle East, Europe, and the Americas that appeared to have the same configuration and internet exposure. They did not confirm any breaches at those six banks.

Quantum Fabric, formerly Kony Fabric, connects digital banking applications to back-end systems such as databases, identity services, and payment APIs.

Temenos Infinity Spotlight runs on top of Fabric and helps bank staff manage user roles and business rules. Temenos reports more than 600 digital banking clients worldwide, but that figure does not indicate how many use the affected configuration.

BankWeaver Hijacks Banking Servers

Investigators traced the breach to an internet-facing Fabric authentication service configured for anonymous rather than private access. Spotlight normally issues an anonymous token before sign-in.

In the compromised deployment, the authentication service treated that token as sufficient and granted administrative access. The attackers did not need to steal or guess a password.

That access let the attackers abuse Fabric’s support for custom Java services. The feature normally allows developers to run approved code as part of an application.

In this case, malicious code ran with the application’s existing permissions and access to internal systems. Researchers identified two malicious Java components: FabricShell and FabricShadow.

FabricShell was a web shell, a backdoor that let attackers run operating system commands and query databases remotely.

BankWeaver Hijacks Banking Servers (Source: forescout)

FabricShadow collected server details, including hostnames, network addresses, Java versions, and service account names. It sent the information to an external server and left a local copy.

Investigators also linked the campaign to more than 30 source IP addresses, many associated with compromised UK home routers and network storage devices.

They suspect the attackers used some compromised systems to stage stolen data. The relationship between BankWeaver and a separate botnet remains unconfirmed.

According to the investigation, Temenos traced the behavior to the service’s access settings and released configuration updates and guidance.

Banks should apply those updates, set privileged authentication services to private, and remove direct internet access to Spotlight and Fabric administration services.

Staff should reach these services through a restricted network or an access gateway that requires multi-factor authentication.

Security teams should look for unexpected Java archive uploads, new integration services, and Java or Tomcat processes launching shells or download tools, forescout said.

Indicators of Compromise (IoCs)

CategoryIndicatorWhere to look
Payload-hosting domainssendit[.]sh, temp[.]sh, plainraw[.]com, plainraw[.]shDNS, proxy, and outbound HTTP logs. The report lists plainraw[.]com in its IoC table but names plainraw[.]sh in the attack narrative. Verify both against your logs.
Payload-hosting IP37.187.78[.]41Firewall, proxy, and network flow logs.

Note: IP addresses and domains are intentionally defanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.

Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team 

The post Hackers Hijack Banking Servers Without Passwords Using BankWeaver Attack appeared first on Cyber Security News.