Alright, that would explain it. It hooks into user32.dll for some window management (GetForegroundWindow() and the like)and uses the handle of client.exe to detect if the client is currently focused for stuff like taking screenshots.

Invader & Invader (loader)
1)What is this?
Starting with version 6 both Kaspersky Anti-virus and Kaspersky Internet Security include a Proactive Defense Module (a behaviour blocker) which can detect suspicious activities based on the behaviour of an application. Invader is the verdict given when a process tries to inject code into another process (code injection). This is to manipulate certain things in it. This coresponds to the option "Intrusion into processes"from the Activity Analyzer settings. Invader (loader) although similar in name to Invader behaves differently. In this case the process tries to inject a module into another process (Dll injection). This coresponds to the option "Window Hooks" the Activity Analyzer settings.

forum.kaspersky.com

Don't see why that would even be an issue. Nobody else has reported anything like that. There seems to be a lot of "pdm.invader" false positives, just look around.

Huh. That's odd.

http://i.imgur.com/DnQFY.png

Kaspersky Anti-Virus is rated as one of the top civilian anti viruses of the year. What's going on here?