This project has moved. For the latest updates, please go here.

Norton Internet Security

Dec 16, 2013 at 7:19 PM
Norton Internet Security complains about the Move Mouse 2.6.2 application does log key strokes. NIS then stopped the Move Mouse application removes the program files entirely.
I used Move Mouse 2.6.1 for some weeks before without any problem.
Today i installed Move Mouse 2.6.2 and got this problem.
Is there any explanation for that? Does anybody else have the same problem?
Dec 17, 2013 at 10:38 PM

There is no key logging code in Move Mouse (yet). You can take a look for yourself by browsing the source code.

It's been downloaded over 2000 times since it was released last week, and this is the first I am hearing of this. I'm afraid I can't really offer an explanation as to why your AV software is complaining about it.

Incidentally - a future version of Move Mouse may have some key logging code so that it can be stopped/started using key strokes. This was a feature that has been requested, although I may have to reconsider ,as I didn't consider that AV software may not like this behaviour.

Are you able to create an exception for Move Mouse in NIS?


Feb 11, 2014 at 7:43 PM
See if the new 3.0.0 release is any better for you.
Feb 17, 2014 at 8:20 AM
Just installed the new Version 3.0.0.

Only seconds later Norton Internet Security complains about a suspicious program and recommends the removal of the program:

Discovered: November 4, 2013Updated: November 4, 2013 9:53:28
PMType: Trojan, VirusInfection
Length: VariesSystems
Affected: Windows 2000, Windows 7, Windows 95, Windows 98, Windows Me, Windows NT, Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP

SONAR.Heuristic.112 is a heuristic detection for processes based on certain attributes.

Files that are detected as SONAR.Heuristic may be malicious. We suggest that you submit any such files to Symantec Security Response. For instructions on how to do this using Scan and Deliver, read Submit Virus Samples.


Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":
Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
Enforce a password policy. Complex passwords make it difficult to crack password files on compromised computers. This helps to prevent or limit damage when a computer is compromised.
Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
If a threat exploits one or more network services, disable, or block access to, those services until a patch is applied.
Always keep your patch levels up-to-date, especially on computers that host public services and are accessible through the firewall, such as HTTP, FTP, mail, and DNS services.
Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
Isolate compromised computers quickly to prevent threats from spreading further. Perform a forensic analysis and restore the computers using trusted media.
Train employees not to open attachments unless they are expecting them. Also, do not execute software that is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised Web site can cause infection if certain browser vulnerabilities are not patched.
If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
For further information on the terms used in this document, please refer to the Security Response glossary.


Feb 17, 2014 at 8:33 PM

Well, there's not really a lot more I can do for you. I can assure you that Move Mouse isn't a virus. You can take a look at the source code yourself to see if there's anything that you find suspicious.

You're options are either to allow an exception for the Move Mouse application in your AV software, or stop using it altogether.

Marked as answer by sw3103 on 3/20/2017 at 2:26 PM