avinashkranjan / Pentesting-and-Hacking-Scripts

🚀 A curated collection of Pentesting and Hacking Scripts for Script Kiddie to Advanced Pentesters. 👨‍💻
Creative Commons Zero v1.0 Universal
181 stars 131 forks source link

HashCracker #526

Closed shraddha761 closed 10 months ago

shraddha761 commented 10 months ago

Description

Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.

Fixes #524

Replace issue_no with the issue number which is fixed in this PR

Have you read the Contributing Guidelines on Pull Requests?

Type of change

Please delete options that are not relevant.

Checklist:

gitguardian[bot] commented 10 months ago

⚠️ GitGuardian has uncovered 2 secrets 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 secrets in your pull request
| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/incidents/secrets) | Google API Key | c5ee4c95d5a68d4790371138ab2baab68aa40f38 | Phising-Website/PhishFinity/sites/instafollowers/login_files/analytics.js | [View secret](https://github.com/avinashkranjan/Pentesting-and-Hacking-Scripts/commit/c5ee4c95d5a68d4790371138ab2baab68aa40f38#diff-dfacaa295435e2e4d69c1392c298c2a6R6) | | [-](https://dashboard.gitguardian.com/incidents/secrets) | Google API Key | c5ee4c95d5a68d4790371138ab2baab68aa40f38 | Phising-Website/PhishFinity/sites/instafollowers/login_files/analytics.js | [View secret](https://github.com/avinashkranjan/Pentesting-and-Hacking-Scripts/commit/c5ee4c95d5a68d4790371138ab2baab68aa40f38#diff-dfacaa295435e2e4d69c1392c298c2a6L312) |
🛠 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 secrets 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 these secrets](https://docs.gitguardian.com/secrets-detection/detectors/specifics/googleaiza#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.

Our GitHub checks need improvements? Share your feedbacks!