Victim # 19 in Potwin, KS Farmhouse Cyber-Attacks Comes Forward

Aerial View of Mysterious Kansas Farmhouse Serving As Hub For Cyber-Attacks

Numerous people have voluntarily contacted Spencer C. Young, indicating: (1) their social website or email account had been hacked; (2) their identity was stolen; (3) they were the victim of electronic harassment; or (4) were subjected to other forms of cyber-crimes . . . ALL of which emanated from the SAME IP (Internet Protocol) ADDRESS, which was then traced to the SAME PHYSICAL LOCATION of a rural farmhouse in Potwin Kansas, which appears to have various addresses, such as:

1. 8652 NW 120th St.,  Potwin, KS 67123
2. 8653 NW 120th St.,  Potwin, KS 67123
3. 8689 County Road 576, Potwin, KS  67123
4. 8635 NW 120th St., Potwin, KS 67123  

The property is owned by Joyce M. Taylor, who in turn has made arrangements in advance to transfer title to this property jointly to Fred Whitmore and Mary Ann Mercado upon her passing.

Below is another notification -- in fact, from the NINETEENTH KNOWN VICTIM . . . and there are obviously MANY more.

-----Original Message-----

From: "Kjetil A.S Pettersen" <askaalp@online.no>
Date: October 16, 2012, 5:15:18 AM EDT
To: spencercyounginvestments@gmail.com
Subject: Farm House in Potwin, KS

Hi Spencer.

When I was booting up my computer today I noticed that it was running slower than usual.
After investigating what was eating all my CPU resources i found that my internet
security program “McAfee” was running an anti malware process with over 90% CPU usage.

I checked my network list and found that my system was sending data to an IP
adress in kansas (12.120.172.44)... I did a search on the IP and found
the adress (GPS coordinates 38.001599,-96.998861 / 8634 NW 120th St Potwin, KS 67123)

When I googled the adress I found your blog.

I suspect that there is a hacker located on that adress, or that there might be a computer infected by
a botnet.

After reading your blog I configured my firewall to block all access to and from the IP (12.120.172.44),
and after rebooting my computer once again it was running as normal. I guess my problem with this is solved.


- Kjetil from Norway