Hitman Pro Support and Discussion Thread

Hmm. Maybe next time we can have a remote look? If you send me a PM then I usually can have a remote look right away.

 

Thank you very much

Need you the File for check and for the analyse

 

Sure if it happerns again i can let you know.

 

All beta's running without problem on Win7 x64.

Just a feature request. I write my own programs and every time I run a scan Hitman Pro wants to upload them to the Scan Cloud. Is it possible to add an "ignore file" option, so on the next scan they are not detected anymore ?

Else, everything oke

 

What's this?
Looks familiar lol

 

I think that this is a copy of HitmanPro to earn money.
Surfright has copyright, now you can use it!

 

A few more EWS) :

 

EWS is not a scan you should run on regular basis.
That said, I'll whitelist these new files.

 

I know but I felt I have to let you know these

 

Hi, maybe somebody can help me.. I did a scan today with Hitman Pro and got the following infection:



I have NOD32 and SUPERAntiSpyware Pro running real time along with Outpost Pro Firewall with Proactive Protection enabled and I have Malwarebytes Pro for on demand and none of those indicate I have an infection. I do have task manager replaced with Process Hacker, however, could that be the reason of the detection and it is a false positive or should I be worried?

It seems to be a registry key so I cannot get to the file to upload to Virus Total..

Thanks

 

I have just installed process hacker and used the option to replace task manager and I get the same FP. I then ran a scan with the task manager replacement option turned off and nothing detected.

 

We constantly fill the cloud with remnants. This one sneaked in. Solved the FP.

 

Thanks!

 

HitmanPro 3.6 Build 159 Released

Changelog

• ADDED: Windows 8 Release Preview support.
• ADDED: Detection and removal of XULRunner redirect scripts.
• ADDED: /fb command line switch to perform Force Breach.
• ADDED: HitmanPro switches the desktop to ensure visibility.
  Some Ransomware use a dedicated desktop to prevent applications from popping up.
• IMPROVED: Force Breach to kill more processes.
• IMPROVED: Force Breach now works under SYSTEM or SERVICE account.
• IMPROVED: Detection and removal of ZeroAccess/Sirefef CLSID variant.
• IMPROVED: Improved removal of MaxSS bootkit.
• IMPROVED: Improved Volume Boot Record (VBR) handling.
• FIXED: A problem where Default scheduled scan would not scan for cookies.
• FIXED: SafeBoot Minimal was not working.
• FIXED: Behavioral scoring on WOW64 uninstall keys.
• FIXED: Compatibility issue with Dataplex caching software from NVELO.
• UPDATED: Portugues language.
• UPDATED: Internal white lists.

Users are automatically updated to the new version.

We've also released a new brochure for use in corporate environments here:
http://files.surfright.nl/hmp-brochure-en.pdf

Also the command line reference has been updated to reflect this version:
http://dl.surfright.nl/hmp-command-line_reference-1_5.pdf

Both documents can also be found here:
http://www.surfright.nl/en/downloads/business

 

I am not sure about this after I updated... Perhaps I should report in the WSA/Prevx forum.

 

I see a galore of threads in the HitmanPro.exe process writing in other process memory. This is NOT part of HitmanPro code so it must be malware doing this.

I addition I see HitmanPro is listing malware (red banner). The malware most likely injected itself in the HitmanPro.exe process and from there is injecting in other processes. That is what I can tell from the WSA event log.

 

HMP scan is only picking up the same detection that I previously, reported, and ignored - https://www.wilderssecurity.com/showpost.php?p=2070183&postcount=4390

The only thing going on is the numerous writes of NVT - SocketSentinal in WSA SecureAnywhere while running a HMP scan. I just don't get it.

 

Then I don't understand the log of WSA as that states that either HitmanPro.exe is writing in other process space or SocketSentinel is writing into HitmanPro.exe process space.

 

As you can see just prior to upgrading HMP, I had first shutdown WSA. I found this is better because I have noted that if I don't, I get freezing of my system, caused by interaction with WSA.

The screenshot below shows the restart of WSA after the HMP upgrade.

Perhaps, I should post in both the other developers' threads, with reference to my posts, here.

 

WSA seems to affect alot legitimate programs (i had the same issue as you too) so i uninstalled WSA. it might ofer the best protection in the world but whats the point when you have to interact with it on a daily basis just to use your machine the way you want? anyway brilliant change-log eric

edit- i will giving away the 1 year WSA licence key. will send by PM to random members if my first PM gets no response.

re-edit= key given away

 

Just updated and running as a "sweet dream" here. 2 's up

 

Have you contacted our support team or me directly about these issues? I would think it would make much more sense to just correct the problem. Also, I would hope you aren't giving away the key which I downgraded specifically for you

 

WSA has cetainly NOT affected any of my other programs negatively...

 

as much as i wanted to keep the key i just could not live with the constant trouble shooting which WSA requires ON MY SYSTEM. am sure its perfectly fine on virtually everyone's computer but there is something inherently wrong with prevx/WSA on my particular system. whether its VLC player, Hitman Pro, Steam, hardware monitoring programs etc, its causing me issues which i dont have the time to troubleshoot (hardware driver conflict with prevx/WSA source code?) so i thought i would do the decent thing and let someone else have the key as they would enjoy it more than i would.

i really appreciate you changing the key for me Joe and it has not gone unappreciated. i still recommend you guys to my clients but on my specific system, its a no go. i wanted to like it but it just was not meant to be.

 

If you or anyone else is having a problem, please write into our support inbox so that we can fix the issue for you.