Started seeing reports from the University of Berkeley again this evening. Specifically 169.229.3.91 which has been observed trying to run shellcode against a rash of servers the last 2 weeks. The activity is very high today. Maybe the "Office of the President" at Berkeley can hire somebody to secure their network. Not that they have ever been breached or anything.
We have a history with reporting on activity at Berkeley. Search our archives for more information.
The purpose of this page is to provide awareness to individuals and organizations that are leaking information and the information of their customers. The entities listed on this site are verified to be leaking personal information sometimes without the company even being aware. SLC Security is now owned and operated by Jigsaw Security Enterprise. We are currently in process and as such this blog will eventually be taken offline and merged with Jigsaw Security resources.
Showing posts with label UC Berkeley. Show all posts
Showing posts with label UC Berkeley. Show all posts
Saturday, June 4, 2016
Sunday, December 14, 2014
UPDATE: UC Berkeley Acknowledge Breach
Previously we reported on a list of college systems that were showing up in our OSINT system as being compromised. Earlier today we were notified that an alert was sent to UC Berkeley students and staff advising them of the breach.
Read our previous post here.
This is exactly why we started this blog and we are glad to see that they reported this in such a timely manner.
From the information being provided it appears as though the Real Estate Division is the affected Berkeley entity. They are stating that they first detected the activity in September. Although UC Berkeley is not a customer of ours we are glad that they took action.
Read our previous post here.
This is exactly why we started this blog and we are glad to see that they reported this in such a timely manner.
From the information being provided it appears as though the Real Estate Division is the affected Berkeley entity. They are stating that they first detected the activity in September. Although UC Berkeley is not a customer of ours we are glad that they took action.
Subscribe to:
Posts (Atom)