Serious Discussion The way I counter infostealers

Victor M

Level 25
Thread author
Verified
Top Poster
Well-known
Oct 3, 2022
1,496
5,568
2,369
InfoStealers are scripts and executables that steal session cookies, browser passwords, docx, and generally all files of interest to an attacker.

I apply the principle of least privilege for this one. Create accounts for different tasks. For example: home budgeting and banking, shopping, aimless browsing, gaming, work etc. You would keep only related files and passwords in each account. So that the infostealer can only steal a subset of things important to you. And the attack surface is also smaller because maybe you'll only encounter infostealers in game cheat sites and you'd be using your gaming account then.

Not convenient. But convenience is the enemy of securitiy always.
 
InfoStealers are scripts and executables that steal session cookies, browser passwords, docx, and generally all files of interest to an attacker.

I apply the principle of least privilege for this one. Create accounts for different tasks. For example: home budgeting and banking, shopping, aimless browsing, gaming, work etc. You would keep only related files and passwords in each account. So that the infostealer can only steal a subset of things important to you. And the attack surface is also smaller because maybe you'll only encounter infostealers in game cheat sites and you'd be using your gaming account then.

Not convenient. But convenience is the enemy of securitiy always.
Your approach makes sense as a damage-limitation strategy.

Why it helps

Using separate standard user accounts for different activities can reduce the impact of an infostealer because:

  • Browser cookies, saved passwords, autofill data, and many app settings are often stored per user profile
  • Documents and desktop files are normally separated by account
  • A compromise in one account does not automatically expose everything stored in another account
  • Risky activity can be isolated from more sensitive activity such as banking or work

So in principle, this is a valid form of compartmentalization.

Important limitation

It is not a complete defense.

If malware executes under one account, it may still be able to:

  • Steal everything accessible to that account
  • Capture keystrokes or clipboard data during that session
  • Abuse active browser sessions
  • Attempt privilege escalation
  • Target shared folders, external drives, and cloud-synced locations

Also, if you frequently switch between accounts or use “Run as administrator” carelessly, some of the isolation benefit is reduced.

What is strong in your model

  • Separating high-value activity like banking from general browsing
  • Keeping fewer files and credentials in each profile
  • Reducing exposure of long-lived sessions and saved logins
  • Using least privilege instead of daily admin use

That is broadly aligned with good security practice.

Where convenience is not the only factor

I would slightly refine the “convenience is the enemy of security always” part.

In practice, poor usability can also weaken security if it causes people to:

  • Disable protections
  • Reuse simple passwords
  • Store credentials unsafely
  • Stop following the process consistently

So the better principle is usually: use as much separation as you can maintain reliably.

More practical additions

If the goal is specifically to reduce infostealer damage, these measures are also useful:

  • Use a password manager instead of storing passwords directly in the browser where possible
  • Enable MFA on important accounts, especially email and banking-related services
  • Keep separate browsers or browser profiles for sensitive and non-sensitive activity
  • Avoid running as administrator for daily use
  • Turn off password saving in browsers used for risky activity
  • Be cautious with downloads, cracks, cheats, and “mods” from untrusted sources, since those are common infostealer delivery paths
  • Keep Windows, browsers, and security software updated

A separate browser profile can sometimes give a large part of the benefit with less friction than fully separate Windows accounts, although full user separation is stronger.

Bottom line

Yes, separating activities across different user accounts is a reasonable way to limit what an infostealer can access. It is a containment measure, not a substitute for prevention, but it can meaningfully reduce damage when used consistently alongside standard security practices.
 
I find @Victor M’s suggestion quite sensible; it’s an extension of browser compartmentalization down to file storage. On a Windows system, you’d have to prevent other accounts from accessing each other’s files, maybe using permissions and EFS (Pro). Volume-mounted encryption tools (like VeraCrypt and Cryptomator) seem easy to miss — you have to unmount before using another account.

That still seems like a lot of work. My cybersecurity and privacy habits, modest by what I have seen suggested here, are already considered extreme by people around me. I’d need more motivation (which I suspect the world would provide) to move in that direction.

I think the simplicity of @Marko's method is very appealing. The caveat is always: don’t miss, and perhaps make any miss likelier to be recoverable.
 
I'm not separating anything. I just don't download anything that isn't coming from reputable source and that's it.
Not going to cut it these days, plenty of times recently I've downloaded a trojan/malware infested program from majorgeeks/softpedia.

From official website? Maybe but the recent supply chain CCleaner & CPU_Z campaigns shows nothing is really secure.
 
Not going to cut it these days, plenty of times recently I've downloaded a trojan/malware infested program from majorgeeks/softpedia.

From official website? Maybe but the recent supply chain CCleaner & CPU_Z campaigns shows nothing is really secure.
I still don't get why would anyone download software from 3rd party websites when official websites exist.

CCleaner is malware on its own, anyway. And attacks on official websites are extremely rare too.

Personally, I don't have bunch of software installed, maybe 10 or so, all popular programs. The less I have installed, the secure I am and less job of maintaing the software I have.
 
InfoStealers are scripts and executables that steal session cookies, browser passwords, docx, and generally all files of interest to an attacker.

I apply the principle of least privilege for this one. Create accounts for different tasks. For example: home budgeting and banking, shopping, aimless browsing, gaming, work etc. You would keep only related files and passwords in each account. So that the infostealer can only steal a subset of things important to you. And the attack surface is also smaller because maybe you'll only encounter infostealers in game cheat sites and you'd be using your gaming account then.

Not convenient. But convenience is the enemy of securitiy always.
Well with that approach you are in good company. 💪

When I recall well Joanna Rutkowska posted in a blog how she used the new Windows UAC in combination with SACL and SRP to spawn (start) different programs in different (limited) users for different purposes. She started for instance outlook using another (limited) user while taking away write rights to system folders for that limited user and blocking execution in shared (user) folders for that user.

She later on told that the idea of Quebes OS was born using (her and) your idea of (application purpose based) least privilege containers (y)
 
Well with that approach you are in good company. 💪

When I recall well Joanna Rutkowska posted in a blog how she used the new Windows UAC in combination with SACL and SRP to spawn (start) different programs in different (limited) users for different purposes. She started for instance outlook using another (limited) user while taking away write rights to system folders for that limited user and blocking execution in shared (user) folders for that user.

She later on told that the idea of Quebes OS was born using (her and) your idea of (application purpose based) least privilege containers (y)
Rehips basically automated, simplified and made a gui for different account usage at the same time. It was a good software, but they would never make enough money to keep it updated and alive.
 
Yeah but then you need to consider a vulnerable update server inside the software, that can be hacked and used to serve malware.

That's why I prefer the internal updater linked to a github account to download updates. Web browsers we have no choice and have to trust.
Absolutely! We do have to take this into consideration as well. But keep in mind that no security software can protect you from this kind of threats as malicious executable file comes from official domain and the file has spoofed digital signature. Again, it's highly unlikely update server of Chrome, for example, would be compromised. The target is usually barely updated software and somewhat less popular one.

Don't be mistaken. GitHub accounts have been taken over before too. This doesn't make you any safer as well.
 
Last edited: