SpyBot infected?

SpyBot infected?

Secure Home | Search | About
 Microsoft Antivirus Discussions    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
SpyBot infected? Marek Kalisz 10-01-2006
---> Re: SpyBot infected? cquirke (MVP Wi...10-07-2006
Posted by Marek Kalisz on October 1, 2006, 1:00 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
This night I downloaded an update to SpyBot the started scan. This download
was from See-Cure #2 (Europe) server. Then, after a few minutes, in about
40% of scan, my AV (G Data AVK) warned me about some virus in Spybot:

Generic.Malware.SYdlg.D42B776F (file: C:\Windows\system32\CloseAll.exe)

I quarantined it immediately, of course. Spybot was halted for a few
minutes, then started to finish scanning again - to the end. And, besied
AV, it was the only program I run at that time.
Now, you can chose SpyBot updates from a few alternate servers. Already in
the past I experienced unsuccessful update of some modules from some of
those servers (wrong sum, for example) so I had to change server to finish
full updates. But - if what happened to me with SpyBot is real it means
that even "anti"s with an excellent renome aren't completely safe.
I might be wrong...
Marek Kalisz



Posted by David H. Lipman on October 1, 2006, 1:25 pm
If you were  Registered and logged in, you could reply and use other advanced thread options

| This night I downloaded an update to SpyBot the started scan. This download
| was from See-Cure #2 (Europe) server. Then, after a few minutes, in about
| 40% of scan, my AV (G Data AVK) warned me about some virus in Spybot:
|
| Generic.Malware.SYdlg.D42B776F (file: C:\Windows\system32\CloseAll.exe)
|
| I quarantined it immediately, of course. Spybot was halted for a few
| minutes, then started to finish scanning again - to the end. And, besied
| AV, it was the only program I run at that time.
| Now, you can chose SpyBot updates from a few alternate servers. Already in
| the past I experienced unsuccessful update of some modules from some of
| those servers (wrong sum, for example) so I had to change server to finish
| full updates. But - if what happened to me with SpyBot is real it means
| that even "anti"s with an excellent renome aren't completely safe.
| I might be wrong...
| Marek Kalisz
|

No. C:\Windows\system32\CloseAll.exe has nothing to do with SpyBot S&D.

Presumeably while you were scanning with SpyBot S&D the file
C:\Windows\system32\CloseAll.exe was scanned and as this happened G-Data AVK
anti virus
software caught this with its "On Access" scanner.



com/got-a-virus.htm



Posted by Marek Kalisz on October 1, 2006, 2:06 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Thanks for explanation. I learned again something new for me...
Marek Kalisz

>
> | This night I downloaded an update to SpyBot the started scan. This
> download
> | was from See-Cure #2 (Europe) server. Then, after a few minutes, in
> about
> | 40% of scan, my AV (G Data AVK) warned me about some virus in Spybot:
> |
> | Generic.Malware.SYdlg.D42B776F (file: C:\Windows\system32\CloseAll.exe)
> |
> | I quarantined it immediately, of course. Spybot was halted for a few
> | minutes, then started to finish scanning again - to the end. And,
> besied
> | AV, it was the only program I run at that time.
> | Now, you can chose SpyBot updates from a few alternate servers. Already
> in
> | the past I experienced unsuccessful update of some modules from some of
> | those servers (wrong sum, for example) so I had to change server to
> finish
> | full updates. But - if what happened to me with SpyBot is real it means
> | that even "anti"s with an excellent renome aren't completely safe.
> | I might be wrong...
> | Marek Kalisz
> |
>
> No. C:\Windows\system32\CloseAll.exe has nothing to do with SpyBot S&D.
>
> Presumeably while you were scanning with SpyBot S&D the file
> C:\Windows\system32\CloseAll.exe was scanned and as this happened G-Data
> AVK anti virus
> software caught this with its "On Access" scanner.
>
>
>
> com/got-a-virus.htm
>
>



Posted by cquirke (MVP Windows shell/use on October 7, 2006, 8:25 am
If you were  Registered and logged in, you could reply and use other advanced thread options
On Sun, 1 Oct 2006 12:00:58 -0500, "Marek Kalisz"

>This night I downloaded an update to SpyBot the started scan. This download
>was from See-Cure #2 (Europe) server. Then, after a few minutes, in about
>40% of scan, my AV (G Data AVK) warned me about some virus in Spybot:

>Generic.Malware.SYdlg.D42B776F (file: C:\Windows\system32\CloseAll.exe)

That can happen when a resident av responds to a "touch" made by an
on-demand scanner. Consider....
- the resident av doesn't recognise a new malware
- the new malware arrives, but may not run (i.e. remains inactive)
- the resident av is updated, now can recognise the malware
- the malware is inactive, so doesn't get detected
- you use a different on-demand scanner, e.g. SpyBot
- this scanner reads the malware file
- this brings the file to the attention of the resident av
- the resident av then detects and managed the malware

There are two other aspects to this.

Firstly, a scanner may be unaware of locations in which other scanners
store their material, and thus detect malware within these stores.
This malware has already been detected and managed, and thus is
unlikely to pose an active threat, but may be detected.

Usually, each scanner takes pains to hide what they quarrantine so
that other scanners can't detect it - but this may fail for various
reasons, and when that happens, you get "new" detections.

Secondly, some management tools may themselves be detected as malware,
either because what they do could be seen as a risk (e.g. password
resetters, product key finders, etc.) or because they may contain
signatures of the malware they clean (e.g. an old GoHip killer that's
often detected as GoHip itself).

>Now, you can chose SpyBot updates from a few alternate servers. Already in
>the past I experienced unsuccessful update of some modules from some of
>those servers (wrong sum, for example) so I had to change server to finish
>full updates.

Yes, I see that often as well, across multiple systems and sites.
Spyware Blaster's updates are equally trouble-prone.

>But - if what happened to me with SpyBot is real it means
>that even "anti"s with an excellent renome aren't completely safe.

Any code can be infected by a generic code-infecting virus, such as
CIH, Magistr, etc. I've often seen av programs infected this way, and
I've also seen systems where the infected file count was massively
higher when the resident av was infected in this way.

If you put on your Matrix-vision glasses, you'll see it's all just
code; the intention of the code is meaningless.

To the user, it's a resident av scanner.

To an attacker, it's an infectable underfootware file-groper with
low-level access to every file on the system.

The only reason we don't see the full impact of this as yet, is that
there are many different resident av out there, with none having such
a dominant market share that it presents a worthwhile target.

This is a large reason why I hope MS will not build an av solution
into the OS, as doing so would take the chocks off such attacks.



>------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
>------------ ----- --- -- - - - -

Posted by Dan W. on October 7, 2006, 10:13 am
If you were  Registered and logged in, you could reply and use other advanced thread options
cquirke (MVP Windows shell/user) wrote:
> On Sun, 1 Oct 2006 12:00:58 -0500, "Marek Kalisz"
>
>> This night I downloaded an update to SpyBot the started scan. This download
>> was from See-Cure #2 (Europe) server. Then, after a few minutes, in about
>> 40% of scan, my AV (G Data AVK) warned me about some virus in Spybot:
>
>> Generic.Malware.SYdlg.D42B776F (file: C:\Windows\system32\CloseAll.exe)
>
> That can happen when a resident av responds to a "touch" made by an
> on-demand scanner. Consider....
> - the resident av doesn't recognise a new malware
> - the new malware arrives, but may not run (i.e. remains inactive)
> - the resident av is updated, now can recognise the malware
> - the malware is inactive, so doesn't get detected
> - you use a different on-demand scanner, e.g. SpyBot
> - this scanner reads the malware file
> - this brings the file to the attention of the resident av
> - the resident av then detects and managed the malware
>
> There are two other aspects to this.
>
> Firstly, a scanner may be unaware of locations in which other scanners
> store their material, and thus detect malware within these stores.
> This malware has already been detected and managed, and thus is
> unlikely to pose an active threat, but may be detected.
>
> Usually, each scanner takes pains to hide what they quarrantine so
> that other scanners can't detect it - but this may fail for various
> reasons, and when that happens, you get "new" detections.
>
> Secondly, some management tools may themselves be detected as malware,
> either because what they do could be seen as a risk (e.g. password
> resetters, product key finders, etc.) or because they may contain
> signatures of the malware they clean (e.g. an old GoHip killer that's
> often detected as GoHip itself).
>
>> Now, you can chose SpyBot updates from a few alternate servers. Already in
>> the past I experienced unsuccessful update of some modules from some of
>> those servers (wrong sum, for example) so I had to change server to finish
>> full updates.
>
> Yes, I see that often as well, across multiple systems and sites.
> Spyware Blaster's updates are equally trouble-prone.
>
>> But - if what happened to me with SpyBot is real it means
>> that even "anti"s with an excellent renome aren't completely safe.
>
> Any code can be infected by a generic code-infecting virus, such as
> CIH, Magistr, etc. I've often seen av programs infected this way, and
> I've also seen systems where the infected file count was massively
> higher when the resident av was infected in this way.
>
> If you put on your Matrix-vision glasses, you'll see it's all just
> code; the intention of the code is meaningless.
>
> To the user, it's a resident av scanner.
>
> To an attacker, it's an infectable underfootware file-groper with
> low-level access to every file on the system.
>
> The only reason we don't see the full impact of this as yet, is that
> there are many different resident av out there, with none having such
> a dominant market share that it presents a worthwhile target.
>
> This is a large reason why I hope MS will not build an av solution
> into the OS, as doing so would take the chocks off such attacks.
>
>
>
>> ------------ ----- --- -- - - - -
> Drugs are usually safe. Inject? (Y/n)
>> ------------ ----- --- -- - - - -


Great point and I had not even considered your final point. I guess the
solution is for Microsoft to continue Live Care and like David points
out the antivirus in live one care is not good enough yet to be
considered and I would continue to stay with products such as AVG
anti-virus.

BTW, Chris -- fixing one of the XP Professional computers at school and
Spybot Search and Destroy destroyed special hidden and planted active
vector deep within the registry that would allow the system to be
compromised by a virus ------------------- I was able to save the system
just in time --------------- Threat Factor Determined to be HIGHLY CRITICAL

Also, some adware and other junk and tightened the settings. Installed
Mozilla Firefox -- safer and more secure solution and computer now in
good shape and of course allowed all files shown and removed the really
weak link of remote assistance and control boxes that were checked.

--
Dan W.

Computer User

Similar ThreadsPosted
w32.spybot.nlx April 14, 2006, 9:29 pm
W32/SpyBot.AAQB December 2, 2005, 8:45 pm
Help With w32.spybot.worm August 24, 2006, 10:47 am
Spybot - does it not advise of upgrades? August 16, 2005, 3:46 pm
Spybot 1.4 corrupted display August 16, 2005, 6:33 pm
MS AntiSpyware vs Ad-Aware vs SpyBot March 3, 2006, 11:32 am
Spybot say REGFIX.EXE is a threat - why? April 5, 2008, 3:29 pm
Spybot Scan Results Question August 16, 2005, 11:19 am
SpywareBlaster and Spybot Search & Destroy. March 1, 2007, 1:29 am
Is AVG 8.0 a/v sweep detecting Spybot S&D innards ? May 10, 2008, 5:43 pm

The site map in XML format XML site map

Contact Us | Privacy Policy