Jump to content
MarkAW

False Positive (Trojan.WinCoDecPRO)

Recommended Posts

I just updated MBAM and ran a quick scan and the result of the scan came back saying my system (XP Pro SP3) has registry infection. I also ran scans with a-squared which came back with nothing , SUPERAntiSpyware also came back with nothing, Avast scan came back with nothing. DR.Wed Cureit came back with nothing

Registry Keys Infected:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe (Trojan.WinCoDecPRO) -> No action taken. [3857535134304144385864454836344564463436414247386152483953563451386146746883808

48071856156747969808884014753613686838370798555708384748079614278667270013974777

0

013889706886857480790148818574807984618566847678728315708970]

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

(No malicious items detected)

Folders Infected:

(No malicious items detected)

Files Infected:

(No malicious items detected)

a-squared Anti-Malware - Version 4.0

Last update: 3/4/2009 9:57:36 PM

Scan settings:

Objects: Memory, Traces, Cookies

Scan archives: On

Heuristics: Off

ADS Scan: On

Scan start: 3/4/2009 10:20:21 PM

Scanned

Files: 1551

Traces: 575793

Cookies: 15

Processes: 34

Found

Files: 0

Traces: 0

Cookies: 0

Processes: 0

Registry keys: 0

Scan end: 3/4/2009 10:22:13 PM

Scan time: 0:01:52

Share this post


Link to post
Share on other sites

This can go either way but more often it looks like it would be a FP and will be removed in the next update .

There is no way that we can tell from the outside if the user has set this key or if malware has .

Share this post


Link to post
Share on other sites

I had a user earlier who said this setting was due to him replacing task manager w\Process Explorer.

Share this post


Link to post
Share on other sites
This should be resolved .

This issue appears to be fixed, but after scanning with 1820, wextract. exe is flagged as "Trojan.Vundo".

Developer mode log:

Malwarebytes' Anti-Malware 1.34

Database version: 1820

Windows 5.1.2600 Service Pack 3

3/5/2009 7:33:45 PM

mbam-log-2009-03-05 (19-33-41).txt

Scan type: Quick Scan

Objects scanned: 58181

Time elapsed: 1 minute(s), 30 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 0

Folders Infected: 0

Files Infected: 1

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

(No malicious items detected)

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

(No malicious items detected)

Folders Infected:

(No malicious items detected)

Files Infected:

C:\WINDOWS\system32\wextract.exe (Trojan.Vundo) -> No action taken. [5253514247403034173621171717182334393639392422172539391822352118181717171822373

61917251717363636363636363636362535393922222535383625182437173635181717171717172

4

22181725202437181717172422173425202437182139382422172120203617383518253939242218

2

13939242218173939242217363939242217253939202234173621171717183939182235361818171

7

171822373619]

Share this post


Link to post
Share on other sites
This issue appears to be fixed, but after scanning with 1820, wextract. exe is flagged as "Trojan.Vundo".

I have the same issue. Posted this one in a new thread

Share this post


Link to post
Share on other sites
I have the same issue. Posted this one in a new thread

Yep.. as you can see there were some issues earlier, so let us hope this one is resolved quickly too!

Share this post


Link to post
Share on other sites

The other problem was fix with the lates update but now i am getting

Malwarebytes' Anti-Malware 1.34

Database version: 1820

Windows 5.1.2600 Service Pack 3

3/5/2009 10:15:04 AM

mbam-log-2009-03-05 (10-15-03).txt

Scan type: Quick Scan

Objects scanned: 59450

Time elapsed: 1 minute(s), 59 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 0

Folders Infected: 0

Files Infected: 1

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

(No malicious items detected)

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

(No malicious items detected)

Folders Infected:

(No malicious items detected)

Files Infected:

C:\WINDOWS\system32\wextract.exe (Trojan.Vundo) -> No action taken. [5253514247403034173621171717182334393639392422172539391822352118181717171822373

61917251717363636363636363636362535393922222535383625182437173635181717171717172

4

22181725202437181717172422173425202437182139382422172120203617383518253939242218

2

13939242218173939242217363939242217253939202234173621171717183939182235361818171

7

171822373619]

Share this post


Link to post
Share on other sites

Thanks guys everything is back to normal.

Malwarebytes' Anti-Malware 1.34

Database version: 1822

Windows 5.1.2600 Service Pack 3

3/5/2009 3:45:01 PM

mbam-log-2009-03-05 (15-45-01).txt

Scan type: Quick Scan

Objects scanned: 59628

Time elapsed: 2 minute(s), 30 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 0

Folders Infected: 0

Files Infected: 0

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

(No malicious items detected)

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

(No malicious items detected)

Folders Infected:

(No malicious items detected)

Files Infected:

(No malicious items detected)

Share this post


Link to post
Share on other sites

Hi All.

This is a known FP, please update your databases and scan again. if you have taken action against the file(s), please restore them from quarantine.

Thanks and sorry for any problems this has caused you .

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.