Safe Mode and spyware

  • Thread starter Thread starter Chiara Popalopa
  • Start date Start date
C

Chiara Popalopa

Well, I have Windows XP (in japanese, maybe that'll help).
I have some spyware and adware ...that I need to get rid off.
I switched to Safe Mode,disable System Recovery, did my things but
when I switch back to normal mode, it is like I didn't do anything,
all my spywares and stuff are back.

Please help.
Thank you.

x-posted.
 
Yes I already have CWShredder, Ad-Aware , Spybot and AVG.
After I get rid off the spywares with them and switch to Normal mode,
it is as if I didn't do anything. I don't understand.
 
It is not unusual to have to run them in both safe and normal mode and also
run them under each user account the loggs into the machines because some of
those thing associate them selves with the "current user's" profile.

1. Run in safe mode with administrator
2. Run in normal mode with administrator
3. Run again in normal mode for each user that uses the machine
 
Note in addition to the good advice from Phillip that these programs are not
always effective against all spyware. There are some horrendously
persistent parasites that neither Ad-aware nor Spybot will remove (some
variants of VX2, look2me, etc.) If you follow Philip's advice and still
have a recurrence, you may need to look for specific removal tools and ask
for help in spyware oriented newsgroups and forums, or to seek professional
help.
--
 
Hi ... Try doing this and see if it help
First thing you should do is download hijackthis and have someone to view
your log , here where you can get hijackthis from

http://www.snapfiles.com/get/hijackthis.html

Here where if you like you can post your hijackthis log for assistance

http://spywarewarrior.com/index.php

http://forums.net-integration.net/

http://computercops.biz/forums.html

Now if you have an Anti-Virus Program which is fairly new ( mostly under a
year )and you are sure that you are still recieving update definitions ?
Then update yours now ....
Then afterward download a few programs , Like these here below

first one is Ad aware ( free Version )

http://www.lavasoft.de/support/download/

Start up this program , What you need to get is the most latest update for
it ,run JUST the "updated" option and afterward close the program for later
use ...

Next program >> Spybot Search and Destroy ( Free )

http://www.safer-networking.net/en/download/index.html

Next Program >> SpywareBlaster ( Free )

http://www.javacoolsoftware.com/sbdownload.html

Next Mcafee Stinger

http://vil.nai.com/vil/stinger/

Okay now perform this operation from this website below

http://support.microsoft.com/?kbid=310405

Okay this is next to perform below :

Click Start. >>Open My Computer. Select the Tools menu and click Folder
Options. Select the View Tab.
Under the Hidden files and folders heading select Show hidden files and
folders. Uncheck the Hide protected
operating system files (recommended) option. Click Yes to confirm. Click OK.
DON'T WORRY ABOUT THE WARNING POP UP WINDOW THIS IS NORMAL , just click yes

Now its time to start your computer in Safe Mode
How to start up in safe mode , there is 2 ways in doing so , just choice one
method only ... Look at this website below

http://www.bleepingcomputer.com/forums/index.php?showtutorial=61#winxo

Okay once in safe mode do the following : Clear out the Temporary internet
files and other temp files.
Go to Start > Settings > Control Panel >Internet Options.
Under the General tab click the Delete temporary internet files,
delete all Offline content as well. Clear out Cookies ... Now close
eveything and be back at your desktop

Now click the start buttom > then the Search/Find option > click Files or
folders > in the named box, type: *.tmp , click search afterward choose Edit
select all -> File > delete.

Empty/delete the entire contents of the C:\Windows\temp folder and C:\temp
folder, (Contents only but not the folder itself.)

This one too if it is there C:\Documents and Settings\username\Local
Settings\Temp\
Delete the recycling bin ...

Now start up Mcafee Stinger and afterward Ad Aware and just basically
perform the options its set at for now ... And remove whatever it finds ...
Start spybor search and destory and do the same with this program
Also with the spyware blaster , just clean what it finds ....

Now use your Anti - Virus Program and run it and see what it finds ...If
your anti-virus finds anything try the repair option first, if that can't be
done then delete the file...
Now restart your computer back to normal mode and reset the setting back
too...Once your computer is up and running do the following :
http://support.microsoft.com/?kbid=310405
and this next >>> :
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/xpsysrst.mspx
Okay after all that was done and you want to be sure its clean go to these
anti virus scan sites and do the scan from each site if you like

http://www.trendmicro.com/download/dcs.asp

http://windowsxp.mvps.org/Scanners.htm

http://www3.ca.com/securityadvisor/virusinfo/scan.aspx
 
Note in addition to the good advice from Phillip that these programs are not
always effective against all spyware. There are some horrendously
persistent parasites that neither Ad-aware nor Spybot will remove (some
variants of VX2, look2me, etc.)

This isn't so much a matter of ineffective cleaners, but rather
reflects the folly of picking a fight with a malware that is already
running (as many are, even in so-called "safe" mode, and even if the
Explorer shell is not running i.e. command prompt only).

The situation is worsened by the duplication of intrusion points
across multiple user profiles - especially if some profiles are
unavailable (stored on server, or unknown passsword, etc.)
If you follow Philip's advice and still have a recurrence, you may need to
look for specific removal tools and ask for help in spyware oriented
newsgroups and forums, or to seek professional help.

The general approach is:

1) Isolate the PC from all networks, including wireless
2) Formally scan to detect "all" malware
3) Read up what you find, for caveats, entry methods etc.
4) Clean it up, taking care of caveats
5) Purge hidden stores; email mailboxes, System Restore
6) Close whatever holes or stupidities that allowed it to enter
7) Re-enable SR
8) Check and update your defences
9) Re-join network when all your other PCs have done (1-8)

The problem is finding a suitable maintenance OS (as well as an av
that runs from it and will find and use updates etc.) that will do (1)
on NTFS. These days, even commercial malware needs that rigor.
 
You must seek updates for Ad-aware and Spybot before running them, each and
every time, even "right out of the box" new. Did you?
 
You give a good summary, but I'm not sure what your point is. The ability
or inability of automated tools to remove severe parasites, IS the measure
of their effectiveness regardless of the reason for it. When they fail, the
extent of manual actions necessary is often far beyond the non-technical end
user including some of the items accurately noted like "Purge hidden
stores", "Close whatever holes or stupidities that allowed it to enter,"
etc. Some of the worst parasites are extremely complex and time consuming
to remove. Your comment re. NTFS access and related issues is quite
right. I sometimes find it useful to put the client's drive as a secondary
in a service machine, or to boot from a Knoppix CD, for cleanup/repair
actions. With severely infected machines, often with expired AV programs,
no critical updates, no firewall, no Spyware protections and dozens or
hundreds of Trojans and parasites (I see these all the time), professional
help to both clean the machine and properly secure it may be a necessity.
--
 
You give a good summary, but I'm not sure what your point is. The ability
or inability of automated tools to remove severe parasites, IS the measure
of their effectiveness regardless of the reason for it. When they fail, the
extent of manual actions necessary is often beyond the non-technical user

Unpalitable but true. So points you can deduce include:
- automated tools cannot be expected to be enough in all cases
- there's more to malware safety than "run an antivirus"
Your comment re. NTFS access and related issues is quite right.

I wish I was wrong there, because this truth is also unpalitable and
hard to live with. When users say "But that's terrible! What can I
do?" it's a drag to have to say 'Sorry, you're stuffed'.
I sometimes find it useful to put the client's drive as a secondary
in a service machine, or to boot from a Knoppix CD, for cleanup/repair

Yep - that's hosted and formal scanning, respecively.

Have you found a good knoppix-hosted av that can pull updates from a
USB stick and scan the whole of an NTFS system? Is the depth of
current Knoppix NTFS support deep enough to manage ADS?

I tried Bit Defender's "Live" a while ago, as it looked like it would
fit the shoes that MS have so far ignored. It was basically Debian
(Knoppix) + the "capture" NTFS support project + Bit Defender.

I've yet to see it complete a full system scan without crashing, and
haven't got as far as getting it to update off USB stick. I did get
Capture to pull NTFS code from USB stick, rather than HD, as is
required if the scanning process is to be formal.
With severely infected machines, often with expired AV programs,
no critical updates, no firewall, no Spyware protections and dozens or
hundreds of Trojans and parasites (I see these all the time), professional
help to both clean the machine and properly secure it may be a necessity.

This is true - and this is the reality that "just wipe and start over"
or "update your av and scan the whole PC" or "go to an online scanning
site" cannot hope to manage effectively.

It's not only end users who read in these forums; there will be techs
too - those with pro interest and expertise in these matters (who will
hopefully correct my mistakes), tech pros who don't yet have expertise
in these matters, and non-pros with an interest, e.g. the geeky
neighbor or the power user in cubicle 7 who are asked to help.

So I don't think tech detail that's over end user's heads should be
excluded in these discussions. As a reader here, this would be the
sort of level that I would be most interested in reading.

Even a PC that had good defences when it was infected, may not
anymore. Not only were those good defences not good enough, but it's
more than likely the malware has broken fences by killing the av,
hijacking the av's update access, and/or disabling the firewall.

So IMO whenever you clean a system, you need to check and fix defences
as well as endevour to block the method that was used to infect the
PC. If you never find out what infected the PC, you can't know how it
got in, and you can't be sure you've blocked it - and that's why I
don't see "wipe and start over" as an effective strategy.


-------------------- ----- ---- --- -- - - - -
"If I'd known it was harmless, I'd have
killed it myself" (PKD)
 
cquirke (MVP Win9x) said:
1) Isolate the PC from all networks, including wireless
2) Formally scan to detect "all" malware
3) Read up what you find, for caveats, entry methods etc.
4) Clean it up, taking care of caveats
5) Purge hidden stores; email mailboxes, System Restore
6) Close whatever holes or stupidities that allowed it to enter
7) Re-enable SR
8) Check and update your defences
9) Re-join network when all your other PCs have done (1-8)

On more than one occasion I was never able to get them cleaned up and it was
quicker to reload the workstation from scratch and take extra measures to
"stupid proof" the machine with jacked up security settings and using
anti-spyware that "immunizes" (at least to some extent) from reinfection. I
am of course still waiting for a better solution, but right now the only
dependable situations I have are machines that don't have humans using them
or machines that have no internet access.
 
cquirke (MVP Win9x) said:
Yep - that's hosted and formal scanning, respecively.

That will scan for files, but unless the Scanner is smart enough to be able
to both find and open the registry files on the drive, the scatter registry
entries won't be cleaned up.
fit the shoes that MS have so far ignored. It was basically Debian

You should probably ask any of the Security MVPs about that, considering
they just flew in from all over the world to spend a week at Redmond to deal
with this stuff back in November. MS is not "ignoring" anything. The issues
is deciding the right approach when you have so may "special interest"
pulling you in different directions when you can only choose one. Home
users want "easy to use" and they want all the "goodies",...some businesses,
especially if heavily "sales" driven want all the features and "security be
damned", other organizations want all the security and the "features be
damned",....and then there is every variation in between those.

There are also "legalities" involved because the users "agreed" to the EULAs
of some of this Spyware at installation time because they weren't sharp
enough to know what they were agreeing to. AV companies like Symantec &
McAfee can face the possibility of law suites for declaring the stuff
"spyware" or other negative names and removing or quarantining it. And
needless to say I think MS has had their "fill" of law suits for a while.
Wether or not those would be defeated is a side issue, companies just don't
want the "cost" or the "publicity" generated from that even if they win the
case.
 
"cquirke (MVP Win9x)" wrote in message
That will scan for files, but unless the Scanner is smart enough to be able
to both find and open the registry files on the drive, the scatter registry
entries won't be cleaned up.

Yep; part of two general problems:
- maintenance OS compatibility with installed OS (Knoppix)
- maintenance OS "sees" the wrong installation (Bart, hosted)

It's possible to build an awareness of these things into a
CDR-bootable NT or installed NT seeing an alien HD for the same time,
but it's not been done so far.

Also, imperfect/incomplete support for the file system can leave
certain items unscanned - and that applies both to mOS and av on it.

There are ways for malware to defend against all three methods of
removal, but malware can't defend itself against formal detection,
because that process doesn't leave any footprints for the malware to
react to. That's why I advocate formal scan, research, then clean.
You should probably ask any of the Security MVPs about that, considering
they just flew in from all over the world to spend a week at Redmond to deal
with this stuff back in November. MS is not "ignoring" anything.

I've pulled down the presentations, and the subject titles do suggest
that we are worried about the same things, which is good.
The issues is deciding the right approach when you have so many
"special interest" pulling you in different directions when you can
only choose one. Home users want "easy to use" and they want
all the "goodies",...some businesses, especially if heavily "sales"
driven want all the features and "security be damned", other
organizations want all the security and the "features be damned"

Some of these issues are easy to play Solomon with. For example;
should XP restart on errors by default, for the benefit of unattended
server use? Under most conditions, the answer is No, because pro IT
will know how to turn on that feature, while Joe Sixpack will not know
where to turn it off. Under one condition - crashes that occur before
the OS has completed booting - the answer is always No. There's no
point in restarting an unbootable OS, you just bit-rot the HD for nil.

But at the end of the tube, there is the one crunch that *defines* the
difference between Home and Pro: Who wins, the guy sitting at the
keyboard, or a notional "admin" on the 'net? Different answers there.
There are also "legalities" involved because the users "agreed" to the EULAs
of some of this Spyware at installation time because they weren't sharp
enough to know what they were agreeing to. AV companies like Symantec &
McAfee can face the possibility of law suites for declaring the stuff
"spyware" or other negative names and removing or quarantining it.

Things are getting murkier here - you have:
- clicked installs that pass through an EULA
- clickless installs that bypass an EULA
- "genuine" commercial software products
- commercial vendors that are out of jurisdiction
- traditional malware faking commercial status as SE
- traditional malware faking commercial status to delay av

Yes, av balk at crunching commercial malware. This has discredited
them and created the anti-cm industry to fill the gap; in fact, the
trend is currently to catch-up by forging alliances with anti-cm, etc.

And yes, commercial malware vendors have sued anti-cm vendors, who
sometimes drop detection as a result.

The solution to this is reposition the anti-cm tool as one used to
remove unwanted software - i.e. tone down the rhetoric so that the cm
vendor has nothing to sue about. All the anti-cm vendor says is "we
offer to remove programs ppl don't want. The fact that ppl have
indicated they don't want your sware and want it removed, is the need
we meet. We make no comment on the value or otherwise of your sware."

MS has been prudent in calling this stuff "unwanted software" rather
than malware or "spyware", to avoid the business plan that goes:
- write commercial malware
- provoke MS into crunching it
- sue MS for the millions you might have made

That's why I don't see "unwanted software" as the same sort of weak
understatement as "prank macro" from the Concept days.

Traditional malware may wave a few commercial signs around, delaying
av response while the av tries to follow these up to figure out
whether the sware is a "real" product or not.

OTOH, one day we'll see a PoC that waves an EULA at the user, which
the user consents to, even tho the malware is classicly "virus". We
have already seen a PoC that describes itself as "This is a VIRUS!!".

For example:

The contents have been password protected to maintain your security.
The password is: "I CONSENT TO WHATEVER THIS VIRUS DOES TO MY PC".


-------------------- ----- ---- --- -- - - - -
Reality is that which, when you stop believing
in it, does not go away (PKD)
 
On more than one occasion I was never able to get them cleaned up and it was
quicker to reload the workstation from scratch and take extra measures to
"stupid proof" the machine with jacked up security settings and using
anti-spyware that "immunizes" (at least to some extent) from reinfection.

In a pro IT environment, the impact of this should be acceptable, as
long as it holds. The worry is; you may end up seeing another 49
cases in the next 24 hours, and wish you'd cracked it the first time!

In consumerland, this "solution" is failure. Typically, the
consumer's PC is the only PC; there are no backups; no-one knows what
sware was installed from where, or what's lost until it's lost.
am of course still waiting for a better solution, but right now the only
dependable situations I have are machines that don't have humans using them
or machines that have no internet access.

In the Win9x days, I never had to "wipe" a system that hadn't hatched
a payload. The expectation was that all infected PCs could be cleaned
up unless a payload had gone off, and those expectations were met. In
some cases (specifically, several tricky/messy intra-file code
infectors), damaged files had to be re-extracted, but this was
possible because av scanning could give a list of affected files.

If this is no longer possible, then from the standpoint of many user's
#1 security concern, we have a considerably worse OS.

I avoid much of the problem by not using NTFS. At least that way, I
have a bigger range of tools that can formally scan all files, thus
providing a safe starting point from which further research and
clean-up can proceed. In most cases, it's safe to do a formal clean
up or rename-away, with some manual settings fixing to do after that.


-------------------- ----- ---- --- -- - - - -
Running Windows-based av to kill active malware is like striking
a match to see if what you are standing in is water or petrol.
 
cquirke (MVP Win9x) said:
If this is no longer possible, then from the standpoint of many user's
#1 security concern, we have a considerably worse OS.

I consider the OS better not worse. Most of the stuff comes in using ActiveX
Controls via ActiveX enabled Browsers. The methods for the most part were
not mostly bugs but were normal functions that were "perverted" by the
mal-ware designers,...and all of this centers around the browser and not the
OS. There is a vast difference between today's XP-sp2 and the old original
Win95, and no one could say that XP is worse.

The largest part of Mal-ware could be stopped by just a few toggles to turn
off ActiveX Controls.
 
cquirke (MVP Win9x) said:
I avoid much of the problem by not using NTFS. At least that way, I
have a bigger range of tools that can formally scan all files, thus
providing a safe starting point from which further research and
clean-up can proceed. In most cases, it's safe to do a formal clean
up or rename-away, with some manual settings fixing to do after that.


You might want to note that this also removes the possibility of using the
features that differentiate NTFS from FAT, particularly the permissions and
owner information(*). Even if you feel that FAT is superior to NTFS because
more drivers are available to read and write FAT from a maintenance disk
(which seems to be your main push), it's important to include the other
advantages of NTFS over FAT before making the key decision to choose one
over the other.

Alun.
~~~~
(*) There are other features, too - quotas, encryption, etc, etc.
 
(Oversnipped: "This" = being able to clean a malware-infected PC)
I consider the OS better not worse. Most of the stuff comes in using ActiveX
Controls via ActiveX enabled Browsers. The methods for the most part were
not mostly bugs but were normal functions that were "perverted" by the
mal-ware designers,...

Firstly, I must mention that I use the word "malware" to refer to all
malware; i.e. the traditional viruses, worms and trojans, plus the
commercial malware often referred to as "spyware".

Next, I would not refer to standard use of offered functionality as
"perversion", but rather the result of the OS/browser vendor's failure
to anticipate the consequences of those functionalities.
and all of this centers around the browser and not the OS.

Infectability through the web, yes. But I wasn't referring to that,
nor was I making the general assertion that NT is a worse OS, or even
the more plausible assertion that NT is a worse consumer OS.

I was specifically referring to the ability to clean an infected PC,
without having to scrap the installation as unsalvigable.

But if you want to talk infectability, then there are those obligatory
networking services that NT waves to the Internet. Win9x is
structurally immune to these direct worm attacks; unless the user had
SQL as a side-effect of Office and was thus prone to Slammer, or has
F&PS bound to Internet on DUN and thus gets Opaserv'd, Win9x users
aren't subject to direct clickless attacks, as NT users are.
There is a vast difference between today's XP-sp2 and the old original
Win95, and no one could say that XP is worse.

The phrase "fitness for purpose" comes to mind - and yes, XP SP2 is
still far less maintaionable than Win9x, esp. if on NTFS. Unless you
bought a PC extremely recently, and thus got a genuine SP2 OS CD, XP
plus SP2 means no Recovery Console and no repair install - because
installing SP2 invalidates the original installation CD.

To address that, one has to create a slipstreamed installation CD. Is
this documented by MS? Sure, at the site. Will the SP2 you install
offer to build this replacement installation CDR for you? Nope.
The largest part of Mal-ware could be stopped by just a few toggles to turn
off ActiveX Controls.

So the original Win95 is pretty good, as it pre-dates ActiveX :-)

--------------- ----- ---- --- -- - - -
Error Messages Are Your Friends
 
"cquirke (MVP Win9x)" wrote:
You might want to note that this also removes the possibility of using the
features that differentiate NTFS from FAT, particularly the permissions and
owner information(*). Even if you feel that FAT is superior to NTFS because
more drivers are available to read and write FAT from a maintenance disk
(which seems to be your main push), it's important to include the other
advantages of NTFS over FAT before making the key decision to choose one
over the other.

Yes - as well as whether those features are as relevant as what you
give away. In fact, it's the baroque features themselves that are
part of the problem; unless properly supported by the maintenance OS,
as well as the av that runs on it, they can offer refuge to malware.

This isn't theoretical anymore; it'salready happening, and reportedly
is even happening with ITW commercial malware.
(*) There are other features, too - quotas, encryption, etc, etc.

I'll reply to you via email, as I may be getting into stuff that isn't
PoC'd or ITW'd yet (and for which we don't have fixes).


-------------------- ----- ---- --- -- - - - -
Hmmm... what was the *other* idea?
 
Back
Top