- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Verizon Hacker:
Feb 21 13:29:51 2010 Inbound Traffic Blocked - Default policy TCP 71.166.167.59:25777->71.117.x.x:139 on ixp0 [repeated 3 times, last time on Feb 21 13:30:00 2010]
Name: static-71-166-167-59.washdc.east.verizon.net
Address: 71.166.167.59
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How are they a hacker? Did they just run a port scan, could be a virus. I would report them to perhaps abuse@verizon.net if you feel this is a constant attack. Perhaps contact tech support and complain. They would hear out your complaint, and see who has the static address asigned to them.
If you google earth the 38.906N, 77.017W location for the IP, it shows on M St NW Washington, D.C. Most likely a Verizon C.O. but who has the static address is the question.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I too have been hammered by almost a DOS attack. Looked at my firewall logs and came up with this. Also reported to security@verizon.net. Restarted my connection to get a new IP.
{edited for privacy}
This was not a static but a dynamic address from a pool.
This data no longer matters because I have a new IP.
Sample from my firewall. Time is UTP. Note source and destination ports. Like a bit torrent machine was attempting a connect.
18:00:14 IN=ppp0 OUT= MAC= src=71.191.55.145 DST=173.66.197.254 LEN=134 TOS=0x00 PREC=0x00 TTL=120 ID=20212 PROTO=UDP SPT=62273 DPT=41989 LEN=114
425 M St NW Washington, DC. Looks like a Verizon CO. Or some non descript Gov building. It is amazing what pictures Google Earth will give you. It even let me zoom in on the Address.
Here is a picture of the building from Google Earth which is where your IP was also.