this post was submitted on 28 Jul 2024
23 points (82.9% liked)

Cybersecurity

9772 readers
2 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 2 years ago
MODERATORS
 

It's the top result if you searched in GitHub about removing Microsoft edge, while it's not detected by Windows Security, Eset or Kaspersky (the best av vendors) it's being detected by other av engines, is it a false positive?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Pika@sh.itjust.works 5 points 2 years ago (1 children)

its running setup.exe with the values --uninstall --system-level --force-uninstall, which sound good as long as the setup.exe is actually the MSedge setup file as it claims, current checksums do not match though, but this could be that the setup was changed from now and when it was added last year, but you can't verify it. That being said, the rest of the code does indeed remove the residue edge from the system, which if the exe wasnt uninstalling it would cause problems as you operated it. That being said, yes you can't verify it without knowing the current setup file version, and having the original to validate the checksum.