for injecting ads into AppValley’s apps), albeit there’s probably more to it (since I can’t reverse/disassemble entire dylib right now), and it was build by user named “justin” who keeps his builds and source code under “/Users/justin/Desktop/AppValley” (on macOS). So, as you can see, this dylib is mostly used for advertisement purposes (i. Username \”justin\” is mentioned at least 14 times in this *.dylib.XCode user path (and username \”justin\”), header files (*.h), and dylib build references.\”Shenzhen Yunxun Technology Co., Ltd.\” certificate (the one AppValley uses) embedded into *.dylib for code signature reasons, probably.I currently don’t have a Mac (or Hackintosh, for that matter will install macOS soon tho) so I can’t use dylib disassembler right now, but I tried to get at least some glance at what’s going on there. See this “dylib.dylib” file on the left? That’s dynamic library, and that’s what developers (or hackers) use for code injection (among other sketchy things). Files in red are these that are not in original IPA (hence the red \”X\” on the right, which means these files exist only in AppValley’s IPA).
Heya, so I decided to do some digging on AppValley’s Spotify++ IPA comparing that to original Spotify++ IPA from Julio Verne (the actual dev behind Spotify++).ĪppValley team injected their own sketchy code into it.ĪppValley’s IPA on the left, original IPA on the right. Official AppValley and TweakBox statement regarding hacked dylibs.Fennikami warns AppValley and TweakBox users.
0 kommentar(er)
