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

Contributing Scan Signatures #1

Open
mitchellkrogza opened this issue Apr 21, 2018 · 2 comments
Open

Contributing Scan Signatures #1

mitchellkrogza opened this issue Apr 21, 2018 · 2 comments
Assignees

Comments

@mitchellkrogza
Copy link
Owner

Anyone who wishes to contribute any scan signatures found in their web server logs, please send a Pull Request on the exploits.list file

@troyengel
Copy link

I'm not sure what this is, Google-fu is failing me - I'm finding hundreds of these attempts per week in my logs:

"GET /admin/assets/js/views/login.js HTTP/1.1" 301 260 "-" "python-requests/2.19.1"

All are coming from one single IP (some 2000 hits in the logs laying around for November) and it's been reported by others here: https://www.abuseipdb.com/check/87.251.81.86 (added my report as well just now)

I think this might be something related to Node.js, but as I can't seem to find definitive information it's unclear if this is a good addition to the exploits.list. I notice a very sharp uptick in my logs starting the week of 2018-11-11 to 2018-11-18, it went from around 10-50 per week before that to 700+ per week starting then, either it was my server "found" by the botnet, or it's some fresh exploit? $0.02 on a "maybe?" that's popped up, hope this helps!

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

No branches or pull requests

3 participants