-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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
Adding a pack for unwanted chrome extensions #3889
Conversation
@Centurion89 has updated the pull request. View: changes |
ok to test |
"BetternetVPN": { | ||
"query": "SELECT * FROM users JOIN chrome_extensions USING (uid) WHERE identifier='gjknjjomckknofjidppipffbpoekiipm';", | ||
"interval": 86400, | ||
"description": "https://www.bleepingcomputer.com/news/security/eight-chrome-extensions-hijacked-to-deliver-malicious-code-to-4-8-million-users/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind wrapping the URLs to additional information in parens similar to the mac attack packs?
"queries": { | ||
"BetternetVPN": { | ||
"query": "SELECT * FROM users JOIN chrome_extensions USING (uid) WHERE identifier='gjknjjomckknofjidppipffbpoekiipm';", | ||
"interval": 86400, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just my 2-cents, but what about doing 3600
for the interval? I feel like for chrome extensions they could be installed pretty quick, and considering this query will likely be enumerating information on client user laptops this query will likely only run once every 3 business days. Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, just had 86400 to be safe :)
- 86400 -> 3600 - Wrap URLs - Remove snapshot
@Centurion89 has updated the pull request. View: changes |
The purpose of this pack would be to track a list of chrome extensions that:
The most straightforward way to track extensions seems to be by identifier. Totally open to feedback on this concept.