Keyloggers: recorded input and account risk
Understand software and hardware keyloggers, what a keystroke recording can expose, and why a clean scan or a different way of entering passwords has limits.
A keylogger is software or hardware that records keyboard input; when used without authorization, it can expose passwords, messages, and other information entered on a device.
Also called: keystroke logger, key logger, keyboard logger, keystroke loggingWhat keystroke logging records
A keylogger captures keyboard input. In a malicious use, that record may reveal information typed while the logger is active, such as account credentials, private messages, or text entered into an application.
NIST SP 800-82 Rev. 3 defines a key logger in the context of obtaining passwords or encryption keys. That publication is an operational-technology security guide; its definition supports the concept, rather than serving as a consumer cleanup procedure.
Imagine a concealed logger active while someone writes a confidential message. Sending the message through a secure service does not address a recording made locally before the service transports it. This is an illustrative distinction between endpoint access and network protection, not evidence that a particular message was captured.
A keystroke record is not necessarily a complete account history or a copy of every file. The logger’s capabilities, access, and active period determine the exposure.
Software and hardware forms differ
A software logger runs through code on the device. A hardware logger is a physical component that records input along a keyboard’s connection or within relevant equipment.
Malwarebytes’ keylogger explanation describes both forms. A suspicious physical component presents a different investigation question from a detected executable.
| Form | Where recording occurs | What an ordinary software scan leaves open |
|---|---|---|
| Software keylogger | Code operating on the device | Whether this particular component was detected and whether it previously recorded data |
| Hardware keylogger | A physical recording component in the input path | Whether the physical setup has been altered |
| Logging function within broader malware | One capability among several | Whether stored data, screenshots, or other information were also collected |
The table describes scope, not a claim that every keyboard or unfamiliar adapter is suspect. Adapters, docks, and approved peripherals are common. On managed equipment, have the responsible team assess unexpected hardware rather than dismantling it or discarding potential evidence.
A clean software scan cannot certify every physical component. Conversely, inspecting a cable does not establish that the operating system has no logging software.
A keylogger is not automatically a virus
Spyware is a broader monitoring category. A malicious keylogger can be one of its mechanisms. An infostealer may instead take stored data without waiting for keyboard input.
A Trojan can conceal or deliver a logging component. A virus is defined by replication through infected hosts. Recording keystrokes does not itself establish that replication mechanism.
A program may also offer logging for an authorized diagnostic purpose. The presence of input recording needs context: who enabled it, who can retrieve the record, which information is included, and whether the monitoring is meaningfully authorized. Device ownership or a commercial product label does not settle every privacy or legal question.
When a security product reports a keylogger, check whether it identified a stand-alone component or a capability within broader malware. The wider component may require more follow-up than the word “keyboard” suggests.
Recording, storage, and transfer are separate stages
A logger may keep recorded information locally, or transfer it elsewhere. NIST’s malware handling guide, published in 2013, describes both retrieval and transfer arrangements.
Detection of logging code does not prove that data was successfully sent, but removing it does not prove that nothing was recorded earlier. Establishing exposure involves the likely active period, the input entered, and available evidence about collection and transfer.
For example, an installer blocked before execution and a running logging component discovered after several account sign-ins are materially different events. Keep that distinction in the report rather than assuming either complete safety or complete disclosure from the category name alone.
Symptoms cannot reliably identify a logger
Typing delay, missed characters, and an unfamiliar process can have ordinary explanations. They are not dependable tests for keylogging. Malicious input capture can also occur while typing feels normal.
Record the exact detection, file location, time, and security action. Use the infection diagnostic when there is only an unexplained symptom. An unexpected account sign-in can justify account recovery, but it does not by itself establish that a keylogger was the cause.
Do not test a suspected logger by typing a password and waiting for a reaction. That exposes more information without producing a reliable diagnosis.
Changing input methods does not settle device trust
Autofill can reduce the need to type particular text. An on-screen keyboard changes how input is entered. Neither establishes that a compromised device is safe for sensitive work: a broader malicious component may capture information through other means.
Likewise, an encrypted website connection protects data in transit rather than removing software on the device. Choose a separate trusted device for sensitive recovery when there is credible evidence of input capture. Treat workarounds as changes to one input path, not as proof that the wider compromise is resolved.
Cleanup and account recovery need coordination
Follow the security product’s supported handling and review what completed. The Windows scanning page provides the site’s software-scan route. If physical recording or managed equipment is involved, arrange an appropriate inspection through a qualified person.
Use the likely exposure period to identify accounts or secrets that need recovery. Follow each provider’s process from a trusted device, including password changes and review of active access where appropriate. Google’s compromised-account guidance illustrates reviewing account events, devices, and security settings.
Removing a logger cannot invalidate a password already copied. Account recovery also does not remove the original recording mechanism. A complete response addresses both and records the evidence that supports the outcome.
Sources & documentation
Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.