user35931: Bitcoin.org seems to be hacked.

How can it be reclaimed, especially since the listed address is receiving a lot of funding?
More importantly, what is the procedure for a new user in establishing trust for bitcoin-related-software(keys for core client, websites etc.)?


user5406: As @1440000bytes already mentioned, Bitcoin doesn't have an official website, although there are numerous sites run by various individuals. Some projects have their own websites such as bitcoincore.org.
The final version of the release will be tagged and signed by one of the maintainers whose keys are listed in bitcoin/blob/master/contrib/verify-commits/trusted-keys. Release candidates are then built by many volunteers from the source code in parallel in our deterministic build process to compare that they create the same binary. The builders' keys, attestations, and instructions how to verify them are found in the release process document. You can find a description of the process here: https://bitcoin.stackexchange.com/a/110517/5406
Older versions of Bitcoin Core releases were signed with the release signing key.
If so inclined, you will find that many of these keys, especially the release signing key, are attested to by other  Bitcoin Core contributors. If this does not suffice, you could put the key into your web of trust by attending a key signing party at a Bitcoin conference.

35931: <p>Bitcoin.org seems to be hacked.</p>
<ol>
<li>How can it be reclaimed, especially since the listed address is receiving a lot of funding?</li>
<li>More importantly, what is the procedure for a new user in establishing trust for bitcoin-related-software(keys for core client, websites etc.)?</li>
</ol>
 5406: <p>As @1440000bytes already mentioned, Bitcoin doesn't have an official website, although there are numerous sites run by various individuals. Some projects have their own websites such as <a href="https://bitcoincore.org" rel="nofollow noreferrer">bitcoincore.org</a>.</p>
<p>The final version of the release will be tagged and signed by one of the maintainers whose keys are listed in <a href="https://github.com/bitcoin/bitcoin/blob/master/contrib/verify-commits/trusted-keys" rel="nofollow noreferrer">bitcoin/blob/master/contrib/verify-commits/trusted-keys</a>. Release candidates are then built by many volunteers from the source code in parallel in our deterministic build process to compare that they create the same binary. The builders' keys, attestations, and instructions how to verify them are found in the <a href="https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#verify-other-builders-signatures-to-your-own-optional" rel="nofollow noreferrer">release process document</a>. You can find a description of the process here: <a href="https://bitcoin.stackexchange.com/a/110517/5406">https://bitcoin.stackexchange.com/a/110517/5406</a></p>
<p>Older versions of Bitcoin Core releases were signed with the <a href="https://github.com/bitcoin/bitcoin/blob/7fcf53f7b4524572d1d0c9a5fdc388e87eb02416/contrib/verifybinaries/README.md" rel="nofollow noreferrer">release signing key</a>.</p>
<p>If so inclined, you will find that many of these keys, especially the release signing key, are attested to by other  Bitcoin Core contributors. If this does not suffice, you could put the key into your web of trust by attending a key signing party at a Bitcoin conference.</p>
