The following instructions have been created to help you to get rid of "PerfectKeylogger" manually.
Use this guide at your own risk; software should usually be better suited to remove malware, since it is able to look deeper.

If this guide was helpful to you, please consider donating towards this site.

Threat Details:

Categories:
  • keylogger

Description:
The Perfect Keylogger often gets installed in a combination with several trojans. Often it is installed in the windows directory and so it is invisible to the user. The Perfect Keylogger records all keystrokes and tries to send them via internet.
Supposed Functionality:
"Do you want to know what your buddy or colleague is typing? Or perhaps you want to check up on your family members and know what they are doing on your computer? With Perfect Keylogger it is possible in just 2 minutes! This program runs on the installed computer, fully hidden from its users, and logs everything that is typed in a protected file. This program runs on the installed computer, being fully hidden from its users, and logs in a protected file all users' typing that occurs. Features list: Can be fully hidden from the user and running permanently Supports all Windows versions, including Windows XP Sending log by e-mail in the hidden mode Can be invisible in Windows NT/2000/XP Task Manager and Windows 9.x/Me Task List Log file is encrypted and can be protected with a password Easy log viewing and management Possibility to specify target applications "
Removal Instructions:

Start Menu:

Please remove the following items from your start menu.
To check where they are pointing to, right-click them and choose "Properties" from the context menu appearing.
  • Items named "Perfect Keylogger Basic Edition.lnk" and pointing to "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\bpk.exe".
  • Items named "Perfect Keylogger Help.lnk" and pointing to "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\bpk.chm".
  • Items named "Uninstall Perfect Keylogger.lnk" and pointing to "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\uninstall.exe".
  • Items named "More useful programs.lnk" and pointing to "*\downloads.url".
  • Items named "Order now!.lnk" and pointing to "*\order.url".

Important: There are more start menu items that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Autorun:

Please use Spybot-S&D, RunAlyzer or msconfig.exe to remove the following autorun entries.
  • Entries named "Profec" and pointing to "<$SYSDIR>\Profec.exe".
  • Entries named "Casulaties" and pointing to "<regexpr>(\S )\\Casulaties\.exe".
  • Entries named "bkav".
  • Entries named "bpk" and pointing to "<$SYSDIR>\bpk.exe".
  • Entries named "explorer" and pointing to "<$SYSDIR>\explorer.exe".
  • Entries named "bpk" and pointing to "<$SYSDIR>\bpk.exe".
  • Entries named "bpk" and pointing to "<$SYSDIR>\bpk.exe".
  • Entries named "bpk" and pointing to "C:\WINDOWS\bpk\bpk.exe".
  • Entries named "bpk" and pointing to "<$SYSDIR>\bpk.exe".
  • Entries named "bpk" and pointing to "<$SYSDIR>\bpk.exe".
  • Entries named "hi" and pointing to "<$SYSDIR>\hi.exe".
  • Entries named "bpk" and pointing to "*\bpk.exe".
  • Entries named "bpk" and pointing to "*\bpk.exe".
  • Entries named "BPK" and pointing to "C:\program files\BPK\BPK.EXE".

Important: There are more autorun entries that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Installed Software List:

You can try to uninstall products with the names listed below; for items identified by other properties or to avoid malware getting active again on uninstallation, use Spybot-S&D or RunAlyzer to locate and get rid of these entries.
  • Products with a key that includes "Perfect Keylogger" in its name or properties.
  • Products that have a key or property named "Perfect Keylogger".

Files:

Please use Windows Explorer or another file manager of your choice to locate and delete these files.
  • The file at "<$PROGRAMFILES>\BPK\bpk.dat".
  • The file at "<$PROGRAMFILES>\BPK\mc.dat".
  • A file with an unknown location named "pk.bin".
  • A file with an unknown location named "pk.bin".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\Profec.exe".
  • The file at "<$SYSDIR>\Profechk.dll".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\bpkr.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\web.dat".
  • The file at "<$SYSDIR>\iexpIorewb.dll".
  • The file at "<$SYSDIR>\iexpIore.exe".
  • The file at "<$SYSDIR>\iexpIorehk.dll".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\rinst.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$PROGRAMFILES>\BPK\bpk.chm".
  • The file at "<$PROGRAMFILES>\BPK\bpkhk.dll".
  • The file at "<$PROGRAMFILES>\BPK\bpki.dll".
  • The file at "<$PROGRAMFILES>\BPK\bpkr.exe".
  • The file at "<$PROGRAMFILES>\BPK\bpkun.exe".
  • The file at "<$PROGRAMFILES>\BPK\bpkvw.exe".
  • The file at "<$PROGRAMFILES>\BPK\bpkwb.dll".
  • The file at "<$PROGRAMFILES>\BPK\downloads.url".
  • The file at "<$PROGRAMFILES>\BPK\inst.bin".
  • The file at "<$PROGRAMFILES>\BPK\install.log".
  • The file at "<$PROGRAMFILES>\BPK\license.txt".
  • The file at "<$PROGRAMFILES>\BPK\order.url".
  • The file at "<$PROGRAMFILES>\BPK\pk.bin".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\kw.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\apps.dat".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\rinst.exe".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\explorer.exe".
  • The file at "<$SYSDIR>\explorerhk.dll".
  • The file at "<$SYSDIR>\explorerr.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$DESKTOP>\Hack Perfect Audition.lnk".
  • The file at "<$PROGRAMS>\Hack Perfect Audition\Hack Perfect Audition.lnk".
  • The file at "<$PROGRAMS>\Hack Perfect Audition\Huong dan.lnk".
  • The file at "<$PROGRAMS>\Hack Perfect Audition\Uninstall .lnk".
  • The file at "<$PROGRAMFILES>\Hack Perfect\ezq.dll".
  • The file at "<$PROGRAMFILES>\Hack Perfect\Hack Perfect.exe".
  • The file at "<$PROGRAMFILES>\Hack Perfect\Huong dan.htm".
  • The file at "<$PROGRAMFILES>\Hack Perfect\Icon.ico".
  • The file at "<$PROGRAMFILES>\Hack Perfect\neverbestboy.sys".
  • The file at "<$PROGRAMFILES>\Hack Perfect\Uninstal.exe".
  • The file at "<$PROGRAMFILES>\Hack Perfect\YNK.cfg".
  • The file at "<$SYSDIR>\bpkhk.dll".
  • The file at "<$SYSDIR>\bpkr.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\web.dat".
  • A file with an unknown location named "HackPerfect..exe".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\bpkhk.dll".
  • The file at "<$SYSDIR>\bpkr.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\bpkwb.dll".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\bpk.exe".
  • The file at "<$SYSDIR>\bpkhk.dll".
  • The file at "<$SYSDIR>\bpkr.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "c:\WINDOWS\bpk\bpk.dat".
  • The file at "c:\WINDOWS\bpk\bpk.exe".
  • The file at "c:\WINDOWS\bpk\bpkhk.dll".
  • The file at "c:\WINDOWS\bpk\bpkr.exe".
  • The file at "c:\WINDOWS\bpk\inst.dat".
  • The file at "c:\WINDOWS\bpk\pk.bin".
  • The file at "<$SYSDIR>\bpkwb.dll".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\bpk.exe".
  • The file at "<$SYSDIR>\bpk.exe".
  • The file at "<$SYSDIR>\bpkhk.dll".
  • The file at "<$SYSDIR>\bpkr.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • A file with an unknown location named "bpk.exe".
  • A file with an unknown location named "bpk.exe".
  • A file with an unknown location named "bpk.exe".
  • A file with an unknown location named "bpk.exe".
  • A file with an unknown location named "bpk.exe".
  • A file with an unknown location named "bpkhk.dll".
  • The file at "c:\WINDOWS\ban.exe".
  • The file at "c:\WINDOWS\banhk.dll".
  • The file at "c:\WINDOWS\banr.exe".
  • The file at "c:\WINDOWS\pk.bin".
  • The file at "c:\WINDOWS\titles.dat".
  • The file at "<$LOCALSETTINGS>\Temp\RarSFX0\AnvilBug.exe".
  • The file at "<$LOCALSETTINGS>\Temp\RarSFX0\AnvilBug.exe".
  • The file at "<$SYSDIR>\bpk.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\web.dat".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "c:\WINDOWS\banwb.dll".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\bpk.exe".
  • The file at "<$SYSDIR>\bpkhk.dll".
  • The file at "<$SYSDIR>\bpkr.exe".
  • The file at "<$SYSDIR>\hi.dll".
  • The file at "<$SYSDIR>\hi.exe".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\mc.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$WINDIR>\USAK1471_251\akII.exe".
  • The file at "<$SYSDIR>\USAK1471_251\akII.exe".
  • The file at "<$SYSDRIVE>\USAK1471_251\akII.exe".
  • The file at "<$DESKTOP>\USAK1471_251\akII.exe".
  • The file at "<$LOCALAPPDATA>\USAK1471_251\akII.exe".
  • The file at "<$LOCALSETTINGS>\USAK1471_251\akII.exe".
  • The file at "<$PROGRAMFILES>\USAK1471_251\akII.exe".
  • The file at "<$WINDIR>\USAK1471_251\AKII.ini".
  • The file at "<$SYSDIR>\USAK1471_251\AKII.ini".
  • The file at "<$SYSDRIVE>\USAK1471_251\AKII.ini".
  • The file at "<$DESKTOP>\USAK1471_251\AKII.ini".
  • The file at "<$LOCALAPPDATA>\USAK1471_251\AKII.ini".
  • The file at "<$LOCALSETTINGS>\USAK1471_251\AKII.ini".
  • The file at "<$PROGRAMFILES>\USAK1471_251\AKII.ini".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\web.dat".
  • The file at "<$PROGRAMS>\Perfect Keylogger Basic Edition\More useful programs.lnk".
  • The file at "<$PROGRAMS>\Perfect Keylogger Basic Edition\Order now!.lnk".
  • The file at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\bpk.chm".
  • The file at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\bsdhooks.dll".
  • The file at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\downloads.url".
  • The file at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\license.txt".
  • The file at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\lview.exe".
  • The file at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\order.url".
  • The file at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic\bpk.dat".
  • The file at "<$SYSDRIVE>\program files\BPK\bpk.chm".
  • The file at "<$SYSDRIVE>\program files\BPK\bpk.dat".
  • The file at "<$SYSDRIVE>\program files\BPK\bpk.exe".
  • A file with an unknown location named "bpk.exe".
  • The file at "<$SYSDRIVE>\program files\BPK\bpkhk.dll".
  • A file with an unknown location named "bpkhk.dll".
  • The file at "<$SYSDRIVE>\program files\BPK\bpki.dll".
  • A file with an unknown location named "bpki.dll".
  • The file at "<$SYSDRIVE>\program files\BPK\bpkr.exe".
  • A file with an unknown location named "bpkr.exe".
  • The file at "<$SYSDRIVE>\program files\BPK\bpkvw.exe".
  • A file with an unknown location named "bpkvw.exe".
  • The file at "<$SYSDRIVE>\program files\BPK\downloads.url".
  • The file at "<$SYSDRIVE>\program files\BPK\inst.bin".
  • The file at "<$SYSDRIVE>\program files\BPK\install.log".
  • The file at "<$SYSDRIVE>\program files\BPK\license.txt".
  • The file at "<$SYSDRIVE>\program files\BPK\order.url".
  • The file at "<$SYSDRIVE>\program files\BPK\pk.bin".
  • The file at "<$SYSDRIVE>\program files\BPK\web.dat".
  • The file at "<$SYSDIR>\dt\2006-10-13_14-02-43-10498531".
  • The file at "<$SYSDIR>\dt\2006-10-13_14-07-43-10798250".
  • The file at "<$SYSDIR>\dt\2006-10-13_14-14-58-11234015".
  • The file at "<$SYSDIR>\dt\th_2006-10-13_14-02-43-10498531".
  • The file at "<$SYSDIR>\dt\th_2006-10-13_14-07-43-10798250".
  • The file at "<$SYSDIR>\dt\th_2006-10-13_14-14-58-11234015".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\inst.dat".
  • The file at "<$SYSDIR>\keystrokes.html".
  • The file at "<$SYSDIR>\kw.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\rinst.exe".
  • The file at "<$SYSDIR>\web.dat".
  • A file with an unknown location named "i_bpk_161_german.exe".
  • The file at "<$PROGRAMFILES>\bpk.exe".
  • The file at "<$PROGRAMFILES>\bpk.dat".
  • The file at "<$PROGRAMFILES>\temporary.bmp".
  • The file at "<$PROGRAMFILES>\th_temp.bmp".
  • The file at "<$PROGRAMFILES>\web.dat".
  • The file at "<$PROGRAMFILES>\pk.bin".
  • The file at "<$PROGRAMFILES>\bpkr.exe".
  • The file at "<$PROGRAMFILES>\bpkhk.dll".
  • The file at "<$SYSDIR>\bpk.exe".
  • The file at "<$SYSDIR>\bpk.dat".
  • The file at "<$SYSDIR>\temporary.bmp".
  • The file at "<$SYSDIR>\th_temp.bmp".
  • The file at "<$SYSDIR>\web.dat".
  • The file at "<$SYSDIR>\pk.bin".
  • The file at "<$SYSDIR>\bpkr.exe".
  • The file at "<$SYSDIR>\bpkhk.dll".
  • A file with an unknown location named "bpk.exe".
  • A file with an unknown location named "bpk.dat".
  • A file with an unknown location named "temporary.bmp".
  • A file with an unknown location named "th_temp.bmp".
  • A file with an unknown location named "web.dat".
  • A file with an unknown location named "pk.bin".
  • A file with an unknown location named "bpkr.exe".
  • A file with an unknown location named "bpkhk.dll".
  • The file at "<$WINDIR>\hh.dat".
  • A file with an unknown location named "i_bpk2003.exe".
Make sure you set your file manager to display hidden and system files. If PerfectKeylogger uses rootkit technologies, use our RootAlyzer or our Total Commander anti-rootkit plugins.
You will have to use a global search for files without a name specified. Be extra careful, because just the name might not be enough to identify files!

Important: There are more files that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Folders:

Please use Windows Explorer or another file manager of your choice to locate and delete these folders.
  • The directory at "<$PROGRAMS>\BlazingTools Perfect Keylogger".
  • The directory at "<$PROGRAMS>\Hack Perfect Audition".
  • The directory at "<$PROGRAMFILES>\Hack Perfect".
  • The directory at "c:\WINDOWS\bpk".
  • The directory at "<$WINDIR>\USAK1471_251".
  • The directory at "<$SYSDIR>\USAK1471_251".
  • The directory at "<$SYSDRIVE>\USAK1471_251".
  • The directory at "<$DESKTOP>\USAK1471_251".
  • The directory at "<$LOCALAPPDATA>\USAK1471_251".
  • The directory at "<$LOCALSETTINGS>\USAK1471_251".
  • The directory at "<$PROGRAMFILES>\USAK1471_251".
  • The directory at "<$PROGRAMS>\Perfect Keylogger Basic Edition".
  • The directory at "<$COMMONPROGRAMS>\Perfect Keylogger Basic Edition".
  • The directory at "<$SYSDRIVE>\Program Files\BlazingTools Perfect Keylogger Basic".
  • The directory at "$PROGRAMS\BlazingTools Perfect Keylogger".
  • The directory at "<$SYSDRIVE>\program files\BPK".
  • The directory at "<$SYSDIR>\dt".
  • The directory at "<$PROGRAMFILES>\BPK".
  • The directory at "<$PROGRAMFILES>\BPK\dt".
  • The directory at "c:\program files\BPK".
  • The directory at "<$COMMONPROGRAMS>\BlazingTools Perfect Keylogger".
Make sure you set your file manager to display hidden and system files. If PerfectKeylogger uses rootkit technologies, use our RootAlyzer or our Total Commander anti-rootkit plugins.
You will have to use a global search for files without a name specified. Be extra careful, because just the name might not be enough to identify folders!

Registry:

You can use regedit.exe (included in Windows) to locate and delete these registry entries.
  • Delete the registry value "IEPK" at "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\".
  • Delete the registry key "hi" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\".
  • Delete the registry key "QSAK" at "HKEY_CURRENT_USER\Software\".
  • Delete the registry key "Perfect Keylogger" at "HKEY_LOCAL_MACHINE\SOFTWARE\Blazing Tools\".
  • Delete the registry key "BlazingTools Perfect Keylogger" at "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu\Programs\".
  • Delete the registry key "{1E1B2879-88FF-11D3-8D96-D7ACAC95951A}" at "HKEY_CLASSES_ROOT\CLSID\".
  • Delete the registry key "{1E1B2878-88FF-11D3-8D96-D7ACAC95951A}" at "HKEY_CLASSES_ROOT\Interface\".
  • A key in HKEY_CLASSES_ROOT\ named "PK.IE", plus associated values.
  • A key in HKEY_CLASSES_ROOT\ named "PK.IE.1", plus associated values.
  • Delete the registry key "{1E1B286C-88FF-11D3-8D96-D7ACAC95951A}" at "HKEY_CLASSES_ROOT\TypeLib\".
  • Delete the registry key "{1E1B2879-88FF-11D3-8D96-D7ACAC95951A}" at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\".
  • Delete the registry key "BlazingTools Perfect Keylogger" at "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu\&Programs\".
If PerfectKeylogger uses rootkit technologies, use our RegAlyzer, RootAlyzer or our Total Commander anti-rootkit plugins.

Browser:

The following browser plugins or items can either be removed directly in your browser, or through the help of e.g. Spybot-S&D or RunAlyzer.
  • Please check your bookmarks for links to "http://giangho.biz".

Final Words:

If neither Spybot-S&D nor self help did resolve the issue or you would prefer one on one help,
  1. Please read these instructions before requesting assistance,
  2. Then start your own thread in the Malware Removal Forum where a volunteer analyst will advise you as soon as available.