Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Banking Trojan
Cyber Security

Banking Trojan

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Cyber Security

A banking trojan is malware built to steal financial credentials and manipulate banking or payment activity on an endpoint. It often combines credential theft, clipboard monitoring, persistence, and command-and-control communication. Modern variants may also gather system details to help attackers tune their targeting and evade detection.

What Makes Banking Trojans Distinct

Banking trojans sit in the malware family, but their purpose is unusually focused: they are designed to interfere with financial activity while remaining hidden on the victim endpoint. That makes them different from broad opportunistic malware because their whole workflow is built around stealing banking credentials, watching transactions, and surviving long enough to monetise access.

Their value to attackers comes from persistence and trust abuse. Once a trojan is resident, it can wait for the user to open a banking session, then observe, alter or redirect activity without needing to break the bank's infrastructure first.

How Banking Trojans Steal and Manipulate Financial Activity

Common techniques include credential theft, clipboard monitoring, form grabbing, browser injection and fraudulent overlays. Some families also intercept one-time codes, hijack remote sessions or swap payment details at the last moment, which turns a legitimate banking action into attacker-controlled fraud.

Because these trojans operate at the endpoint, they can see data after it has been decrypted in the browser or app. That makes them effective against controls that protect traffic in transit but do not harden the user device or browser session itself.

Modern variants often collect system fingerprints, locale, browser data and security tooling information. That reconnaissance helps attackers tune payload delivery, decide when to activate, and evade sandboxing or analyst scrutiny.

Delivery, Persistence, and Evasion Patterns

Banking trojans are commonly delivered through phishing attachments, malicious downloads, fake installers, malvertising or trojanised software. The initial infection is usually only the first step, because the malware then tries to establish persistence and blend into normal user activity.

Persistence can involve registry changes, scheduled tasks, services, browser hooks or other startup mechanisms. Evasion may include obfuscation, environment checks, delayed execution and selective activation, all of which reduce the chance that a security product will flag the sample before it reaches a banking session.

For defenders, the important point is that the infection path and the fraud path are often separated in time. A compromise may remain dormant until the attacker sees a valuable financial opportunity.

Why Banking Trojans Matter to Defenders

These threats are dangerous because they combine endpoint compromise with transaction abuse. In practice, that means the attacker does not need to defeat the bank's backend controls if they can corrupt what the user sees, what the browser sends, or which payment destination is approved.

Defence therefore depends on more than malware scanning. Endpoint hardening, browser isolation, application control, credential protection, device telemetry and transaction verification all matter because the trojan's objective is to manipulate a trusted financial workflow, not simply to plant a malicious file.

For background on the malware class, see Malware Guide. For the trojan family itself and related delivery and detection patterns, see Trojans Guide. Endpoint-focused variants such as QakBot are covered in QakBot Malware Guide.

Risk and Threat Considerations

Banking trojans are high-impact because they turn a single endpoint compromise into a direct path to financial fraud. The main threat is not just stolen credentials, but live manipulation of sessions, payee details, authentication flows and transaction outcomes while the victim believes the workflow is legitimate.

Failure mechanism: The malware succeeds when it can persist on the endpoint, observe active banking use, and interfere with browser or application behaviour before the transaction is finalised.

Impact: This can lead to account takeover, unauthorised transfers, credential reuse across other services, and wider exposure if the infected endpoint is also used for email, corporate access or payment approvals.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8, NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1056 — Input CaptureBanking trojans steal credentials and bank inputs from user sessions.
T1114 — Email CollectionBanking trojans often arrive through phishing and malicious delivery chains.
Recommendation — Map observed input capture to T1056 and hunt for credential theft on endpoints. Correlate delivery activity with T1114-linked campaigns and harden mail filtering.
CIS Controls v8CIS-8 — Audit Log ManagementEndpoint and banking fraud detection depends on collecting and retaining usable telemetry.
CIS-10 — Malware DefensesBanking trojans are malware families that require layered prevention and detection controls.
Recommendation — Centralise logs from endpoints and browsers so trojan activity can be detected and investigated. Deploy malware defenses and tune them for persistence, injection and credential theft behaviour.
NIST SP 800-53 Rev 5SI-3 — Malicious Code ProtectionBanking trojans are malicious code that must be blocked, detected and contained on endpoints.
AU-6 — Audit Record Review, Analysis, and ReportingFraud and endpoint compromise need analysis of logs from browsers, hosts and security tools.
Recommendation — Use SI-3 to detect, block and quarantine banking trojan payloads and related artefacts. Review audit records for persistence, clipboard abuse and transaction manipulation indicators.
OWASP ASVSV16 — Security Logging and Error HandlingTransaction and session abuse become visible only when security events are logged well enough to inspect.
Recommendation — Instrument security logging so suspicious banking session behaviour can be investigated quickly.

Practitioner Guidance

Why practitioners should care: Banking trojans are best handled as both an endpoint threat and a fraud-control problem. If monitoring only looks for file-based malware, the more dangerous behaviour, session manipulation and payee tampering may be missed.

What to watch for: Unusual browser hooks, suspicious child processes, unexpected clipboard changes, new persistence artefacts, and financial sessions that behave differently from the user's normal device and network profile are all worth investigation.

Practitioner takeaway: Treat endpoint trust as part of transaction integrity, because the safest banking session is one the trojan never gets to influence.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org