App Review Webroot SecureAnywhere 2024

[bazang]

However it used to create an ungodly large file (I forgot what it was called) and I had to clear that folder up every week or so. That file was a few gigs in size.

The file = "Journaling File", which records most of the actions performed on the system (in the registry and the file system).

Webroot is OK. I can make it work and work quite well. I just do not need it and choose not to use it. If I had a system with low CPU and primary memory then I would use it.

I use F-Secure and then harden Windows. I do not use an Admin account. I set up the system and I never change it. The security choices I make work for me. I do everything from coding to OSINT to forensics to pentesting. All the tool sets. I do not encounter breakages very often. The methods I utilize can work for others if they are willing to put some effort into it. If not, then they can play musical security software games until they find something that works for them.

Security is not software. It is a process.

 

[Trident]

I will be testing Webroot today, just because of this new WRYES module which is unknown, new and undiscribed.

 

[Trident]

Unfortunately, I got no WRYES here. Inspected all folders and files.
According to SpyShelter, there is a process WRYES.exe. I do not have that.

What is WRYES.x64.exe (Webroot SecureAnywhere)? 4 reasons to/NOT trust it

What is WRYES.x64.exe (Webroot SecureAnywhere)? 4 ways to quickly check if this executable (process) is safe or a virus.

www.spyshelter.com

 

[likeastar20]

Unfortunately, I got no WRYES here. Inspected all folders and files.
According to SpyShelter, there is a process WRYES.exe. I do not have that.

What is WRYES.x64.exe (Webroot SecureAnywhere)? 4 reasons to/NOT trust it

What is WRYES.x64.exe (Webroot SecureAnywhere)? 4 ways to quickly check if this executable (process) is safe or a virus.

www.spyshelter.com

This made me check mine and I had it yesterday, I spotted it in Task Manager. Now I can't see it anymore.

 

[Trident]

This made me check mine and I had it yesterday, I spotted it in Task Manager. Now I can't see it anymore.

My guess is WRYES stands for Webroot (something) Evasion Shield which blocks advanced script attacks. Well, no evasion shield yet here.

 

[likeastar20]

My guess is WRYES stands for Webroot (something) Evasion Shield which blocks advanced script attacks. Well, no evasion shield yet here.

I found it's location

C:\ProgramData\WRCore\CoreService\Component\YARA\WRYES.x64.exe, it's there on my PC. I'm running Webroot beta.

 

[Trident]

I found it's location

C:\ProgramData\WRCore\CoreService\Component\YARA\WRYES.x64.exe, it's there on my PC. I'm running Webroot beta.

I'm afraid I could not get the beta, due to being banned on the forum. Can I have the installer somehow?

 

[ForgottenSeer 114834]

I'm afraid I could not get the beta, due to being banned on the forum. Can I have the installer somehow?

Making friends are we lol.

 

[Trident]

Making friends are we lol.

They banned me "proactively" from the first post.

 

[Trident]

OK, thanks to @likeastar20 I am now equipped with Foreign Code Shield!!!!

Thanks mate!

Still waiting for WRYES to appear though.

 

[ForgottenSeer 114834]

They banned me "proactively" from the first post.

Oh I understand.. id rather walk than ride that popularity train myself. Hive mentality just doesn't jive with me, I like to think for myself and very capable of doing so.

 

[trujax]

OK, thanks to @likeastar20 I am now equipped with Foreign Code Shield!!!!

Thanks mate!

Still waiting for WRYES to appear though.

I haven’t tried Webroot in years, but the Business Endpoint had, or maybe still does have, several shields that were not available in the home products. It was pretty inexpensive if I recall.

 

[tofargone]

Making friends are we lol.

toooo funnny

 

[tofargone]

Is anyone going to test the "NEW" Improved Webroot?

 

[cartaphilus]

Unfortunately, I got no WRYES here. Inspected all folders and files.
According to SpyShelter, there is a process WRYES.exe. I do not have that.

What is WRYES.x64.exe (Webroot SecureAnywhere)? 4 reasons to/NOT trust it

What is WRYES.x64.exe (Webroot SecureAnywhere)? 4 ways to quickly check if this executable (process) is safe or a virus.

www.spyshelter.com

You have been judged by the Webroot God and found wanting. You were not worthy!


I have to dig up some of my old lic boxes and see if it will be accepted as a valid code. Might as well create a snapshot and install it on a system that's running eset and see if they will play nicely together if mutually excluded.

 

[Trident]

Is anyone going to test the "NEW" Improved Webroot?

I do not have access to the "improved" Webroot, but the non-improved is not doing very well. The product has exceptionally high detection on executables, but on MSI and other files it suffers. I have now decided to test the business version, which is not too expensive. It offers all the shield, plus system-wide web blocking (which for now is not in home products). Let's see what the business version can do.

 

[ForgottenSeer 114834]

I do not have access to the "improved" Webroot, but the non-improved is not doing very well. The product has exceptionally high detection on executables, but on MSI and other files it suffers. I have now decided to test the business version, which is not too expensive. It offers all the shield, plus system-wide web blocking (which for now is not in home products). Let's see what the business version can do.

View attachment 284744

Did you go to the location and manually check the detection to make sure it's not traces? NPE is that aggressive sometimes.

 

[Trident]

Did you go to the location and manually check the detection to make sure it's not traces? NPE is that aggressive sometimes.

It is not traces, the malware was active in memory. And there was plenty more (scripts) not detected by NPE either. Webroot has Script Shield and Foreign Code Shield that are supposedly meant to deal with this. But they don't.

 

[ForgottenSeer 114834]

It is not traces, the malware was active in memory. And there was plenty more (scripts) not detected by NPE either. Webroot has Script Shield and Foreign Code Shield that are supposedly meant to deal with this. But they don't.

Had to ask from the single screenshot. I'm betting that gets over looked a lot in here, but assume that you are thorough.

 

[likeastar20]

I do not have access to the "improved" Webroot, but the non-improved is not doing very well. The product has exceptionally high detection on executables, but on MSI and other files it suffers. I have now decided to test the business version, which is not too expensive. It offers all the shield, plus system-wide web blocking (which for now is not in home products). Let's see what the business version can do.

View attachment 284744

Wondering how long it would take to be detected while running in memory