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.

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

Create get_recent_victims.py #100

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

akshayjain-1
Copy link

The following code grabs the data for the "Recent Victims". The code will check if there is an associated domain present for the victim, if yes, it'll add it to the final list - results.json. In case if the domain is not present, it'll check for the corresponding company name, perform a google search and grab the first url. It'll then extract the domain from the url and finally present you with a list of domains for all recent victims

@JMousqueton
Copy link
Owner

When I try the script with only one entry I've got :

HTTPError: 429 Client Error: Too Many Requests

@akshayjain-1
Copy link
Author

When I try the script with only one entry I've got :

HTTPError: 429 Client Error: Too Many Requests

I made some changes and uploaded the modified script.
Added some sleep timers to avoid the error which you got and made some formatting changes in which the data is stored in the csv file.

Also tested the updated code just now and it ran successfully.

Hope this helps.

Updated the code to use a more generic approach for finding the url and removed the dependency on 'class' variable
Copy link

gitguardian bot commented May 25, 2024

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- Generic Password 0e8c455 data/Darkside/20210413.json View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants