Recommended Posts

Just found this little file on one of my storage drives, and remember having a bit of fun with it years ago

The file is a tiny 78kB, extract it using 7zip to find the extracted file is now 21MB, now extract that file and you`ll see that the extracted file is now 2.8GB

How many times can you extract Googolplex before you or your machine gives up ? :D

Apparently there is a file hidden at the very end of all of the extractions but I have never managed to get that far, from what I remember it is a text file containing the entire numerical value of a Googolplex

Download (Extract each file with 7zip)

http://localhostr.co...G/googolplex.gz

Link to comment
https://www.neowin.net/forum/topic/1122198-googolplex-how-far-can-you-get/
Share on other sites

Why post this? Its not a malicious file at all, it does nothing to your AV, there is no executable file at all

And it doesn't try to kill your system with a huge decompression, each extraction gets bigger and you can choose to cancel the extraction at any point

Read the wiki it will show why he did it

Most Anti Virus should not allow you to do this as it "should" pick it up as a zip bomb because of the way it exponentially increases in size

Read the wiki it will show why he did it

Most Anti Virus should not allow you to do this as it "should" pick it up as a zip bomb because of the way it exponentially increases in size

I did read it, Its not a zip bomb

You don't suddenly get 100 Petabytes trying to decompress, each time you extract the file it gets bigger and offers no harm to the machine at all, it doesn't try to crash your system whatsoever

I did read it, Its not a zip bomb

You don't suddenly get 100 Petabytes trying to decompress, each time you extract the file it gets bigger and offers no harm to the machine at all, it doesn't try to crash your system whatsoever

Yes, if you manually extract it the file doesn't expand until you initiate the next nested level, but the the same wouldn't be true for an AV program. For the AV it would initiate the next step automatically in order to ensure the contents of the file are safe. As a result, it would continue going down a level until it exploded.

  • Like 1

Assume a text file with 1 byte per character, the numerical value of a Googolplex would be (1e100) + 1 bytes which is ten duotrigintillion bytes or 9.095e87 terabyes. There isn't enough digital storage on earth to hold this value.

  • Like 1

Yes, if you manually extract it the file doesn't expand until you initiate the next nested level, but the the same wouldn't be true for an AV program. For the AV it would initiate the next step automatically in order to ensure the contents of the file are safe. As a result, it would continue going down a level until it exploded.

There are no file extensions on any of the nested levels, probably to prevent that happening

You dont understand whats being said

AV will auto scan the next level will see its also a zip and scan the next level, will see its a zip and scan the next level will see its a zip and scan the next level

it will continue to do this thus is scanning a bigger and bigger file each time it does this

You dont understand whats being said

AV will auto scan the next level will see its also a zip and scan the next level, will see its a zip and scan the next level will see its a zip and scan the next level

it will continue to do this thus is scanning a bigger and bigger file each time it does this

Funny, every time I ever extracted this, on many machines, with many other people also having a go, not once with different AVs did it cause any problems

Don't like it, don't download it, I wouldn't post any file that would cause problems

Funny, every time I ever extracted this, on many machines, with many other people also having a go, not once with different AVs did it cause any problems

Don't like it, don't download it, I wouldn't post any file that would cause problems

Then you guys had AV software that's actually worth a cent.

A good AV scanner should always stop after a certain time to not trick itself into zip bombs.

Apparently this isn't standard by now? Lord in heaven...

Glassed Silver:mac

I just tried expanding the first level (which produced several .zip files) and Windows (SearchFilterHost.exe) started using all my 8GB of RAM.

I had to terminate the Search Indexer process and then delete the .zip files via the command line.

Pretty scary stuff!

interesting...I've never seen this type of thing before. If I have time later tonight, maybe I'll write a little java program to extract it. It should be easy to extract each layer in memory and just discard each byte as it's read. that way, it wouldn't matter how large the file is. You could just let your cpu churn away. Has anyone tried this just for giggles?

edit: haha what am I talking about. this would never work. I'd run of memory during the extraction. ignore my entire idiotic comment

Then you guys had AV software that's actually worth a cent.

A good AV scanner should always stop after a certain time to not trick itself into zip bombs.

Apparently this isn't standard by now? Lord in heaven...

Glassed Silver:mac

I`m using NOD32 and it gives the all clear, and as you saw in VirusTotals scan, 0% of all scanners found any issues / zip bomb

Previous AVs I've used include Avast and Avira <<< High FP detection rate too but nothing

I just tried expanding the first level (which produced several .zip files) and Windows (SearchFilterHost.exe) started using all my 8GB of RAM. I had to terminate the Search Indexer process and then delete the .zip files via the command line. Pretty scary stuff!

There is only 1 file per extraction, the first = 21MB only

interesting...I've never seen this type of thing before. If I have time later tonight, maybe I'll write a little java program to extract it. It should be easy to extract each layer in memory and just discard each byte as it's read. that way, it wouldn't matter how large the file is. You could just let your cpu churn away. Has anyone tried this just for giggles?

edit: haha what am I talking about. this would never work. I'd run of memory during the extraction. ignore my entire idiotic comment

I remember when I first found this, someone did something similar to what you are thinking, managed to partially extract all of the layers and found the txt file at the end - which is how I know what is in there

  • Like 2

Assume a text file with 1 byte per character, the numerical value of a Googolplex would be (1e100) + 1 bytes which is ten duotrigintillion bytes or 9.095e87 terabyes. There isn't enough digital storage on earth to hold this value.

To expand on this, the volume of the Earth is roughly equivalent to the volume occupied by 2.87e24 3.5" hard drives.

Let's say you stored the .txt file across 1 petabyte 3.5" hard drives (don't exist, but pretend they do) you would still need 8.882e84 hard drives, which would take up a volume of space approximately 1e63 times that of earth itself, if my math is correct.

I remember when I first found this, someone did something similar to what you are thinking, managed to partially extract all of the layers and found the txt file at the end - which is how I know what is in there

yea actually, it looks like it should be possible to do that. Java has a class called ZipInputStream (http://docs.oracle.com/javase/1.4.2/docs/api/java/util/zip/ZipInputStream.html) that can read a stream of bytes and inflate it. He probably had a method to inflate a few bytes into a buffer and then make a recursive call with that buffer. You'd have to make sure there aren't so many recursive calls that you'd get a stack overflow, but eventually, you'd get to the inner most level.

This topic is now closed to further replies.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!