# Googles RNG Hacked

<figure><img src="/files/JaSTihRkQX037YAPE8gG" alt=""><figcaption></figcaption></figure>

Ivan Ludvig's blog post ["Hacking Google Random Number Generator"](https://ivanludvig.github.io/tech/google-random) explores the limitations of the pseudo-random number generator used by Google's `Math.random()` function in browsers. Ludvig describes how the function, based on the xorshift128+ algorithm, can be manipulated to predict future outputs by using Python and the Z3 library. This vulnerability arises because the generator’s sequence can be determined if the internal state is known. Ludvig demonstrates the method to reconstruct the seed from outputs and predict future numbers, highlighting the importance of not using `Math.random()` for cryptographic purposes due to its predictability.

Sp8de's blockchain technology and Quantum Random Number Generators (QRNG), could indeed offer a solution to the vulnerabilities found in `Math.random()`. By providing a decentralized and cryptographically secure source of randomness, Sp8de could enhance the security and unpredictability of number generation processes, especially in applications where the integrity of random numbers is crucial, such as in cryptographic and gaming applications. This would mitigate the risks associated with predictable pseudo-random number generators used in many standard computing environments.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sp8de-docs.gitbook.io/s-p-8-d-e-or-white-paper/vulnerability-of-decentralized-rngs-to-cyber-attacks/googles-rng-hacked.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.