New answers tagged hacking
Regarding your log and your pastebin, it seems to be an automated attempt to test for remote code execution vulnerability. 1) The file a2.png may not be a malware. The hacker want only test if he can access the folder and upload in it a file. If successful, this can signify the hacker that he can execute code and traverse the system folders. 2) Your log ...
You can use Aerodump-ng to monitor all wireless traffic for signal strength. If you know the temporary MAC of the source, start a capture by issuing "airodump-ng [interface]" where [interface] if the name of your wireless device. As you get closer to the source, the "PWR" will increase.
I have a lot of respect for Jenny's answer, but I thought I had to add this: It's an attempt to do a shellshock attack (with grateful thanks to Iain for pointing this out). Provided you've patched your server against this vulnerability, the web server returns a 400, which takes it microseconds of CPU, and thinks no further on the matter. But you write ...
Yes, they are trying. And failing. You can tell that they are failing by looking at the return code -400 - bad request means that your server is basically saying "No way I'm going to let you do that". Which, in this context, is a good thing.
Top 50 recent answers are included