<center>https://images.hive.blog/DQmTjA2YurzfHQnUi9Rc29hmVGe3zmJuhrAGezc32Cd9zRb/image.png
<sub>[src](https://cdn.pixabay.com/photo/2020/08/13/16/55/hacker-5485843__340.png)</sub></center>

In the past few weeks I found <a href="https://hive.blog/hive-139531/@keys-defender/new-feature-code-injections-attempts-detection-xss-sql-injections-csrf#comments">some XSS vulnerabilities</a> in some Hive tools.
After reporting them to witnesses and devs that maintained those apps, I decided it would be helpful to add to @keys-defender's list of weapons the ability to timely detect potential code injection attempts. This should mitigate the issue of attackers targeting the Hive ecosystem of apps and tools.

<br>This bot now uses the following to try to detect potential malicious code published in blocks:

~300 fragments of code for <b>XSS (Cross Site Scripting)</b>

~50 fragments of code for <b>SQL injections</b>

~20 fragments of code for <b>CSRF (Cross Site Request Forgery)</b>

~ ...

These dictionaries will grow in size and be adjusted based on false positives.

<center><sub>Logs of the new code injection detection feature</sub>https://images.hive.blog/DQmW5po4MKUSEsMHiRCnPoGCs13KpBkEoc7b1oCmeuknyeB/image.png
</center>

<br>

If the code injection is attempted in a post or comment (eg. this [test comment of mine](https://hiveblocks.com/x/@b0t5-testing/demo-xss-39533453)), the author will now receive an immediate reply from this bot:<center>
<sub>Logs for code injection checks</sub>
https://images.hive.blog/DQmSSnN5gxiHhoLCsFwy92ALsG4R3FiDL6xRAKWXScVuZVS/image.png</center>

<center><sub><br>Example of @keys-defender's reply</sub>
https://images.hive.blog/DQmUWWMhXSnmDdkWPRGXMecCeqhe3hdDLxgz8D1ozj4t9aY/image.png</center>

<br>A notification is also immediately sent to my [Discord server](https://discord.gg/SXuwsH7) so that I or witnesses and volunteers in it can investigate and react accordingly to report and fix the targeted website or tool. 

Clearly if a bad actor was indeed trying to compromise a website, their account name would also been  known because, as per the blockchain design, past blocks cannot be edited or deleted.


<center>
<sub>Discord notification example</sub>
https://images.hive.blog/DQmVbGu83dSUaNBkHYcEgFKxTFpDeEd1AkSiakXsFnrkFwc/image.png</center>


<br><br>A whitelist is also in use so that known Hive apps devs like @louis88 won't be bothered while testing dapps for vulnerabilities.
<center><sub>My own code injection attempt ignored because I'm on the whitelist</sub>
</sub>https://images.hive.blog/DQmV9DXk47xi8xJ3urs4BkZ1mukyhuf3RsijVurNFKa2TV4/image.png</center>


<br>Stay tuned for more updates and please feel free to suggest new features and improvements! 😎

-----
-----

<div class="pull-left">
<sub><b>Keys protection main features:</b></sub>
<br>- <sub><a href="https://hive.blog/steem/@gaottantacinque/the-keys-defender-bot-is-live-in-beta-mode">Introductory post for @keys-defender launch</a></sub>
<br>- <sub><a href="https://hive.blog/steem/@keys-defender/successfullyprotected-1599725656390">Automatic-posts</a> on leak detection, <a href="https://hive.blog/hive/@keys-defender/successfullyprotected-1600122002275">weekly reports</a></sub>

<sub><br><b>Other features:</b></sub>
<i>-</i> <sub><a href="https://hive.blog/hive/@keys-defender/new-feature-phishing-detection-and-auto-reply">Phishing protection</a></sub>
<i>-</i> <sub><a href="https://hive.blog/hivedev/@keys-defender/new-feature-added-to-keys-defender-plagiarism-detection">Re-posting detection</a></sub>
</div>

<div class="pull-right">
<sub><b>My past security disclosures (from most recent):</b></sub>
<br>- <sub><a href="https://hive.blog/hive/@gaottantacinque/xss-found-in-one-of-drako-s-websites-will-add-details-after-it-s-patched">XSS vulnerabilities in scribe.hivekings.com</a></sub>
<br>- <sub><a href="https://hive.blog/hive/@gaottantacinque/hiveblockexplorer-com-is-vulnerable-to-stored-xss">XSS vulnerabilities in hiveblockexplorer.com</a></sub>
<br>- <sub><a href="https://hive.blog/steemit/@gaottantacinque/steemit-got-hacked">Malicious ads redirecting all Steemit iOS users to a phishing site</a></sub>
<br>- <sub><a href="https://hive.blog/security/@gaottantacinque/steemit-chat-is-unsafe">Reverse tabnabbing and clickjacking in steem.chat and steeemit registration page</a></sub>
</div>

-----
-----

<div class="pull-left"><h5>To support this bot..<br></h5>
- <b><sub>Delegation links:</sub></b><br>
<sub><a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=10%20SP">10 HP</a> <a href="20 HP</a>https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=20%20SP">20 HP</a> <a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=30%20SP">30 HP</a> <a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=40%20SP">40 HP</a> <a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=50%20SP">50 HP</a><br><a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=100%20SP">100 HP</a> <a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=200%20SP">200 HP</a> <a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=500%20SP">500 HP</a> <a href="https://hivesigner.com/sign/delegateVestingShares?delegator=&delegatee=keys-defender&vesting_shares=1000%20SP">1000 HP</a></sub></div>

<div class="pull-right"><br>- <b><sub>Curation trail</sub></b>
<br><sub><sub>Follow @keys-defender's curation trail to upvote all its posts with a fixed vote weight.
HOW: search "keys-defender" on Hive.Vote: https://hive.vote/dash.php?trail=keys-defender&i=1</sub></sub></div>