Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

what about the memory-reading token grabbers #8

Closed
VenTaz opened this issue Jul 25, 2021 · 3 comments
Closed

what about the memory-reading token grabbers #8

VenTaz opened this issue Jul 25, 2021 · 3 comments

Comments

@VenTaz
Copy link

VenTaz commented Jul 25, 2021

No description provided.

@andro2157
Copy link
Owner

Im aware of them. It currently won't protect you from them. (Even though they represent a small amount of public grabbers).

I actually made a working memory-reading grabber POC a while ago. And I'm looking for a way to patch it.

One naive way of preventing it would be to call SetSecurityInfo in the Discord process, to protect it like DTP. But that messes up with the chromium multi-process structure.

@VenTaz VenTaz closed this as completed Jul 26, 2021
@VenTaz
Copy link
Author

VenTaz commented Jul 26, 2021

:/

@andro2157
Copy link
Owner

Fixed in dev-8, now blocking memory reading grabbers (that are not running with admin privileges of course)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@andro2157 @VenTaz