Security Blog

The latest news and insights from Google on security and safety on the Internet

Malware? We don't need no stinking malware!

24 de outubro de 2008
Share on Twitter Share on Facebook
Google

10 comentários :

Twain Harte Vacation Rental Guy disse...

I think it's a great idea. One thing I think is important tho is to not take so long to do a reconsideration request.

It took over 30 days to get a reconsideration request on one of my sites...

27 de outubro de 2008 às 22:46
Unknown disse...

Great source of information. Even though my site not affected with this vulnerability. Some of the sites i got links from have affected and shows such dangerous download caption in yahoo site explorer. Does it affect my website performance in Google SERP?

28 de outubro de 2008 às 03:50
DSchrader disse...

It would be great to have some statistics - how many searches result in such warnings, how many marketed sites are there, changes over time, breakout by infection type (SQL injection, flash exploits, browser exploits . . . )

Also, how this compares with Yahoo's siteadvisor.

29 de outubro de 2008 às 13:44
Arisol disse...

Looking for someone to let me know of any insurance carriers insurance can be purchased for "vishing" attacks to a financial institution. I'm new to this blog-thing (it's an age thing, I'm sure) and am likely in the wrong area.

3 de novembro de 2008 às 14:07
Unknown disse...

For those that do own a site that gets infected with malware it is important to discover how the site was attacked. So that the compromise does not reoccur.

Using open source and freely available tools you can get a pretty good picture of your servers / sites security status.

HackerTarget.com has a number of online scans available using nikto, sqlix, nmap and openvas to check for any obvious vulnerabilities.

27 de janeiro de 2009 às 06:38
Anônimo disse...

I just did a google search to find out why suddenly every single result for every single search I do in Google comes up with this malware warning.

Guess what, even this blog is infected.

Glass houses, stones?

31 de janeiro de 2009 às 09:51
wail of ignorance disse...

Google's malware warning is broken. Today (Jan. 31, 2009), from a google search, EVERY site (including this blog) is blocked with a malware warning. Please fix it right away, google folks!

31 de janeiro de 2009 às 10:06
Dan disse...

Great information on securing website. Really helpful..i also found one more small article on securing website and webhosting

http://softwareinnews.blogspot.com/2009/06/tips-to-secure-your-website-from.html

25 de junho de 2009 às 06:01
Unknown disse...

If one subdomain is hacked, you result in a flag that results in the blocking of the entire root domain on Firefox and other applications. This is unacceptable, if, for instance the hack was to a CMS on one subdomain that isn't on any other. This can result in loss of millions of dollars for publishers and is unacceptable. Be more targeted in your blocking. Additionally, your review request should result in a re-test instantly. Time is money.

3 de julho de 2009 às 18:34
Siddhi disse...

Hi

Pls help me
my site showing "Reported attack site" in ff.

I inform google about it but my problem didnt solve.

My domain is www.earnestjohn.com

Thanks,
Siddhi

7 de maio de 2010 às 05:36

Postar um comentário

  

Marcadores


  • #sharethemicincyber
  • #supplychain #security #opensource
  • android
  • android security
  • android tr
  • app security
  • big data
  • biometrics
  • blackhat
  • C++
  • chrome
  • chrome enterprise
  • chrome security
  • connected devices
  • CTF
  • diversity
  • encryption
  • federated learning
  • fuzzing
  • Gboard
  • google play
  • google play protect
  • hacking
  • interoperability
  • iot security
  • kubernetes
  • linux kernel
  • memory safety
  • Open Source
  • pha family highlights
  • pixel
  • privacy
  • private compute core
  • Rowhammer
  • rust
  • Security
  • security rewards program
  • sigstore
  • spyware
  • supply chain
  • targeted spyware
  • tensor
  • Titan M2
  • VDP
  • vulnerabilities
  • workshop


Archive


  •     2025
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2024
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2023
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2022
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2021
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2020
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2019
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2018
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2017
    • dez.
    • nov.
    • out.
    • set.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2016
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2015
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2014
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2013
    • dez.
    • nov.
    • out.
    • ago.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2012
    • dez.
    • set.
    • ago.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2011
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
  •     2010
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • mai.
    • abr.
    • mar.
  •     2009
    • nov.
    • out.
    • ago.
    • jul.
    • jun.
    • mar.
  •     2008
    • dez.
    • nov.
    • out.
    • ago.
    • jul.
    • mai.
    • fev.
  •     2007
    • nov.
    • out.
    • set.
    • jul.
    • jun.
    • mai.

Feed

Follow
Give us feedback in our Product Forums.
  • Google
  • Privacy
  • Terms