DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

CA: Viruses stole City College of San Francisco data for over a decade before being detected

Posted on January 13, 2012 by Dissent

Nanette Asimov reports:

Personal banking information and other data from perhaps tens of thousands of students, faculty and administrators at City College of San Francisco have been stolen in what is being called “an infestation” of computer viruses with origins in criminal networks in Russia, China and other countries, The Chronicle has learned.

At work for more than a decade, the viruses were detected a few days after Thanksgiving, when the college’s data security monitoring service detected an unusual pattern of computer traffic, flagging trouble.

Read more on San Francisco Chronicle.


Related:

  • Snowflake Loses Two More Bids to Dismiss Data Breach Plaintiffs
  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they? (1)
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • How a hacking gang held Italy’s political elites to ransom
  • NY: Gloversville hit by ransomware attack, paid ransom
Category: Breach IncidentsEducation SectorMalwareOf NoteU.S.

Post navigation

← Podiatrist Used the Identity of 200 Nursing Home Patients to Submit False Bills
Hacktivism, Friday edition: Dutch sites →

1 thought on “CA: Viruses stole City College of San Francisco data for over a decade before being detected”

  1. major tom says:
    January 20, 2012 at 11:09 am

    ahhhh the Russian Business network. The RBN was quite the vile place to get directed to, as it used to serve a whole lot of badware ( bad adware – start out with small simple gifts, then cars, then eventually porn links) it hosted zeno tecnico as well. Zeno would build shares through use of shortcuts and if anyone with a higher priveledge logged on to a workstation, it would connect the badware from computer to computer. it was some pretty bad stuff.

    It sounds like this report is much like anything else. Added verbage suggests that this COULD have acessed the servers in question – they were unsure. It looks like the condition started out in a lab, and from there may have spread.

    Reporters, if thats what you want to call them, need to stick to the facts. They over inflate the initial reports in order for the story to catch the publics’ eye and then qhen questioned about the particular issue, they say “thats what my source said”. Stinkers.

    My questions are:
    1. Ten years? Don’t they periodically check logs, servers or infrastructure for issues?
    2. How about antivirus updates ? If these boxes were able to pass data back to the bad sites, they should have been able to grab Antivirus updates as well.
    3. In a typical lab environment, workstations and laptops are occasionally reimaged, or even replaced on a semi reliable schedule. If these laptops or workstations have been around for over 10 years, without any IT maintenance, then the IT staff needs a stiff kick in the pants.

    Though the RBN may appear to be down, I bet they have pulled up chocks and have moved to parts unknown and have re-established themselves. What they were doing was illegal, but I am sure they made alot of money, and found another ISP that puts up with them as long as the bills are paid, the ISP doesn’t care.

    Purchase a few network appliances that can be employed near the perimeter of the network that can look for nasty addons and websites and help the campus become a little less likely to get attacked. It offers centralized management and pretty graphics so even the executive level personnel can see if they have in issue to resolve.

    Status Quo is never a good idea in Network security or IT management.

Comments are closed.

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.