Embedded Files
THIS SITE WILL BE UPDATING VERY FREQUENTLY<SUBSCRIBE TO OUR YOUTUBE CHANNEL TO GET THE LATEST INFO OR ANNOUNCEMENT!
Note: Open in full screen for dextensify to work properly.
The project only works using home wifi or using a vpn.(file based lisence won't be properly downloaded and function) Error==because? =="fortinet"
Dextensify
read this
read this
Disclaimer:
I do not build or own this project.This web app was being created by ading2210,an refresh idea from {LTMEAT 115+}from Bypassi.
========================================================About(dextensify):
the project was developed based on an unpatchable Exploit /bug working on chrome os/chrome broswer.(It should remains unpatched for later version of chrome broswer or chrome os because it was hanging the extensions physically by TONS of IFRAMES)It truly disable the extensions which are force download by your guardians or organisations.
========================================================About(This exploit):
This is an UNPATCHABLE Exploit/bugs that most of the broswers will have.(It should remains unpatched for later version of chrome broswer or chrome os because it was hanging the extensions physically by TONS of IFRAMES)Chrome os/broswer wants to give there user a smooth enjoyable experience by setting a memory limit to the whole system operation or broswer tabs.(the memory limits for the tabs that runs on the backgrounds to those tabs which you are using will be different )When a project which was running in the backgrounds hits it's memory limit,chrome freeze the tab/background activities along with all extensions.
HOW TO USE
Follow official instructions if you meet configurations below.
processor with four cores/threads and above
six gigs of memory and above
============================================================================
If your device does not meet the configurations above,follow my rules.
1.First open chrome://extensions in a new tab,leave it open.
2.open a new tab and search anything(crazygames,poki),leave it open
3.GO to the setting page for the extensions that you want to disable,Find the"allow access to file urls" button
4.GO back to the dextensify page,click the "freeze extensions" button Immediately switch back to the extension page.
5.On the extension page,quickly spam the"allow access to file urls" buttons for 1-2 seconds and immiediately switch to the new tab page or your system still crashes even staying on the extensions page.
6.Immediately click on the links that you have searched on the new page.
7.Stay on the page and wait 30seconds-1minute for your device to resolve itself.
8.Leave the Dextensify page open,let it run for 2-4 minutes before closing the page.(Dextensify will still be running in your background but it improves device performance greatly,The extensions should be still be freezed and unresponsive)
=======================================================================
special note from the developer:
Every time you restart your computer,you have to repeat the proccess above to be able to freeze the extensions again.
My method should disable extensions for 20-40 minutes before the page get blocked again.
DO NOT GO BACK TO THE DEXTENSIFY PAGE OR IT INSTANTLY CRASHES YOUR SYSTEM.
If you want a longer freeze time ,after operating dextensify for 3 min,plz add 20 or more new tabs and close the whole page.This will longer the freeze time to 1-3 hours
IF YOU HAVE ISSUES ABOUT IT,WATCH THE YOUTUBE VIDEOS DOWN BELOW
DIG DEEPER:ALL YOUR QUESTIONS HERE !
A Refresher on LTMEAT:
A Refresher on LTMEAT:
All resources that belong to a Chrome extension share the same process. Thus, if any of the extension's pages were to freeze, then the entire extension would also be frozen. The easiest way to achieve this would be to navigate to chrome://hang in the address bar, which hangs the current page. However, simply hanging a Chrome extension has the side effect of also freezing any event listeners, blocking any other webpages from loading.
To get around this, you can kill the extension's process right after you hang it (using chrome://kill), then hang it again to prevent the listeners from being registered. By preventing the extension from reloading, then you've functionally disabled it.
Getting Around the Patch:
Getting Around the Patch:
The patch that Chrome v115 included simply disabled the use of chrome://kill and chrome://hang (as well as a few related URLs), and the underlying issues were not fixed. So how do we accomplish the same things without using any Chrome URLs?
Killing an extension is fairly straightforward. On the details page of an extension in chrome://extensions, there's a switch which toggles an extension's access to file:// URLs. Simply flipping that switch will kill the extension's process and force it to restart.
Hanging an extension is slightly trickier, although just like with the original LTMEAT, a convenient Chrome feature makes this possible.
Web Accessible Resources:
Web Accessible Resources:
If you've ever viewed an extension's manifest.json, you may have seen a field called web_accessible_resources somewhere towards the bottom of the file. The purpose of this is to allow other pages to view some of the extension's resources. For instance, if an extension contained the following in its manifest, then any path under chrome-extension://extensionidhere/public/ would be accessible to any regular webpage.
"web_accessible_resources": [
"public/*"
]
Any web accessible resources can also be put inside an iframe. However, since all extension resources share a single process, any iframe of an extension resource will be part of the main extension process. Thus, by constantly creating new iframes to a web accessible resource, you can effectively freeze the entire extension. Since you are able to do this from any webpage, this allows us to bypass the chrome://hang block.
Implementing the Exploit:
Implementing the Exploit:
Obviously, you can't endlessly create iframes without the browser running out of memory and freezing. Previously created iframes have to be removed, although it's not as simple as just calling .remove() on them. Chrome also doesn't seem to be able to properly garbage collect removed iframes (and when it does, it happens after a delay), which leads to a memory leak.
language about
language about
The project is made possible with ninety-three percent of html languages,and 3 percent of python languages.
special Thanks to
special Thanks to
AG7 ,developer of (haoze unblock G7)
I am glad that we have made this project finally availble for everyone,after cooperating with the developer of this site.I am also glad to see that it is finally ready to the pubilcs after facing just so many issues and bugs on the project when running it with our featured dynamic engine(beta).And a thank to you guys for using and supporting the sites!
Another tHanks to
Another tHanks to
Tech supports team/developer------haoze
The problem that was happening was caused by web engine----dynamic dev.(beta) which breaks html based web app like dextensify.Our tech support/developer team was finally able to provide a solution to the project after downgrading the web engine from dynamics (beta) to dynamics.
DISCLAIMER
=============================================================================================
THIS IS FOR EDUCATIONAL PURPOSE,I DO NOT HAVE RESPONSIBILITY IF YOU GET IN TROUBLE FOR USING THE TOOLS ON THIS SITE
It could take time to loadup the page for the first time------BE PATIENT!
I am not one-hundred percent sure about if the project is going to work on different device
strictly follow the instructions given on the exploit
I DO NOT OWN OR HOST THIS PROJECT.THE PROJECT WAS FORKED FROM GITHUB AND SHOULD NOT BE TRADED IN ANY MONETARY WAYS.
Page updated
Report abuse