Create get_recent_victims.py

[akshayjain-1]

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]

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

HTTPError: 429 Client Error: Too Many Requests

[akshayjain-1]

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.

[gitguardian[bot]]

⚠️ 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 | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/workspace/194815/incidents/secrets) | | Generic Password | 0e8c45533ca1a5a4906454ab1bd649e5d2d13c83 | data/Darkside/20210413.json | [View secret](https://github.com/JMousqueton/ransomware.live/commit/0e8c45533ca1a5a4906454ab1bd649e5d2d13c83#diff-873eb38683648c42bbadcac4871879f871d374a73e584decd817fe9a6991c193R206) |

🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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 - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}