|
· Overview ·
|
Overview |
|
Vendor Notes: |
The ActivityX custom control is designed to allow an application access to the powerful facilities of windows journaling. Possible applications of this include macro recording and playback abilities within an application, building simple CBT applications,recording scripts for application testing, automating repetitive tasks or using as an alternative to the sendKeys command. Sets of recorded messages can be stored to file and played back later at either recorded speed or high speed. All messages can be recorded or this can be restricted to keystrokes only. Messages can be recorded relative to the position of a specific window by setting a RelativeToHwnd property at run time, this being of particular importance to messages whose effect depends on the cursor position such as mouse clicks or drag over events. Playback of messages can be aborted by pressing the ESC key or this feature can be disabled by setting a property in the control. |
Category: |
Key Logger: (Keystroke Logger). A program that runs in the background, recording all the keystrokes. Once keystrokes are logged, they are hidden in the machine for later retrieval, or shipped raw to the attacker. The attacker then peruses them carefully in the hopes of either finding passwords, or possibly other useful information that could be used to compromise the system or be used in a social engineering attack. For example, a key logger will reveal the contents of all e-mail composed by the user. Keylog programs are commonly included in rootkits and RATs (remote administration trojans). |
Similar Pests: |
Key Logger |
Origins |
|
Date of Origin: |
September, 1994 |
Operation |
|
Storage Required: |
|
Risks |
|
Detection Issues: |
Difficult to detect by design. May hide from process list. May install with variable names in variable locations. |
Detection and Removal |
|
Automatic Removal: |
|
Manual Removal: |
Follow these steps to remove ActivityX Custom Control from your machine. Begin by backing up your registry and your system, and/or setting a Restore Point, to prevent trouble if you make a mistake. |
| Unregister DLLs: Unregister these DLLs with Regsvr32, then reboot: | |
| Remove Files: Remove these files (if present) with Windows Explorer: | |
Research |
|
File Analyses: |
|
More Info: |
|
Research By: |
|
Last Revised: |
January 24, 2005 |