php.net listado como suspeito - visitar este site pode danificar seu computador

Question

Quando eu acesso o php.net através da pesquisa do Google, recebo a seguinte mensagem dizendo

O site à frente contém malware!

Veja a captura de tela anexada abaixo:

É o mesmo para vocês? Como posso evitar isso?

Isso significa que o site foi invadido ou atacado por malware?

    

Answer 1

Isso ocorre porque o Google realizou uma verificação regular no website nos últimos 90 dias. Os resultados foram isto:

Of the 1513 pages we tested on the site over the past 90 days, 4 page(s) resulted in malicious software being downloaded and installed without user consent. The last time Google visited this site was on 2013-10-23, and the last time suspicious content was found on this site was on 2013-10-23.

Malicious software includes 4 trojan(s).

Malicious software is hosted on 4 domain(s), including cobbcountybankruptcylawyer.com/, stephaniemari.com/, northgadui.com/.

3 domain(s) appear to be functioning as intermediaries for distributing malware to visitors of this site, including stephaniemari.com/, northgadui.com/, satnavreviewed.co.uk/.

Isso ocorre provavelmente porque as pessoas estão deixando links para esses sites em php.net .

    

Answer 2

Há mais nisso. Há relatos (1100 GMT 2013-10-24) de que os links foram injetados no Javascript que o site usa e, portanto, é hackeado por enquanto.

Até que você ouça de maneira diferente, eu evitaria o site. Em breve - tudo ficará bem, sem dúvida.

    

Answer 3

E se você acessar a página de diagnósticos da Navegação segura , você pode ver isso:

Para sublinhar:

Este site não está listado como suspeito no momento.

Eles corrigiram isso enquanto eu publicava essa resposta.

    

Answer 4

Do ponto de vista do php.net, parece um falso positivo:

link

On 24 Oct 2013 06:15:39 +0000 Google started saying www.php.net was hosting malware. The Google Webmaster Tools were initially quite delayed in showing the reason why and when they did it looked a lot like a false positive because we had some minified/obfuscated javascript being dynamically injected into userprefs.js. This looked suspicious to us as well, but it was actually written to do exactly that so we were quite certain it was a false positive, but we kept digging.

It turned out that by combing through the access logs for static.php.net it was periodically serving up userprefs.js with the wrong content length and then reverting back to the right size after a few minutes. This is due to an rsync cron job. So the file was being modified locally and reverted. Google's crawler caught one of these small windows where the wrong file was being served, but of course, when we looked at it manually it looked fine. So more confusion.

We are still investigating how someone caused that file to be changed, but in the meantime we have migrated www/static to new clean servers. The highest priority is obviously the source code integrity and after a quick:

git fsck --no-reflog --full --strict

on all our repos plus manually checking the md5sums of the PHP distribution files we see no evidence that the PHP code has been compromised. We have a mirror of our git repos on github.com and we will manually check git commits as well and have a full post-mortem on the intrusion when we have a clearer picture of what happened.

    

Answer 5

Última atualização (no momento de postar esta resposta)

link

We are continuing to work through the repercussions of the php.net malware issue described in a news post earlier today. As part of this, the php.net systems team have audited every server operated by php.net, and have found that two servers were compromised: the server which hosted the www.php.net, static.php.net and git.php.net domains, and was previously suspected based on the JavaScript malware, and the server hosting bugs.php.net. The method by which these servers were compromised is unknown at this time.

All affected services have been migrated off those servers. We have verified that our Git repository was not compromised, and it remains in read only mode as services are brought back up in full.

As it's possible that the attackers may have accessed the private key of the php.net SSL certificate, we have revoked it immediately. We are in the process of getting a new certificate, and expect to restore access to php.net sites that require SSL (including bugs.php.net and wiki.php.net) in the next few hours.