

partners who pay for promotion by the app) products/software for opening files. All such a tool is likely to do is try to steer their users towards their own and affiliated (i.e. Yeah, in a world without the internet such a utility could have some use, but with the modern web such an app has little utility, at least in my opinion. The mere fact that an app co-opts how the system handles thousands file types in order to provide functionality that does not require that is sufficient for PUP detection at the very least. If you want to see deeper information, there are apps or existing system functionality for those things as well. You can also use the file command in the Terminal if the extension is missing, invalid, or doesn't match the file type. For example, if you want to find out what kind of app will open a file, you can simply Google the extension. Some claim to be able to give you information about a file, but there are other ways to do that that do not require hijacking legit system functionality. This overrides the way macOS is designed to handle such cases, which means that these apps are attempting to divert the user away from Apple's guidance and towards whatever guidance they provide.įurther, such apps serve no real purpose. This is a form of illicit persistence, in that the app will open any time a document is opened that doesn't already have a default handler. As Al points out, these apps register as handlers for just about every existing file type.
