Activator URL scheme detected #107
Comments
|
Thx for the info, it should be fixed in https://github.com/securing/IOSSecuritySuite/releases/tag/1.9.11 |
|
Hey @kyledold, have you found which app caused this false detection? |
|
@tymurmustafaiev unfortunately no, we never found the route cause of what was trigger this. @r3ggi what was the fix? |
rpanichkin
added a commit
to rpanichkin/IOSSecuritySuite
that referenced
this issue
Feb 14, 2024
philbluefox
added a commit
to philbluefox/IOSSecuritySuite
that referenced
this issue
Aug 7, 2024
* new checks added + dropping support for iOS 10 * Update README.md * minimum deploy target changed to iOS 11 * Shadow detector now detected :-) * Update IOSSecuritySuite.podspec * Add support for checking the Parent process id * Resolve various swiftlint warnings * Add checking for known OpenSSH and checkra1n open ports * Add addional checking for [FridaGadget, frida, libcycript] libraries * check for existence of Suspicious Files with [stat(), fopen(), access()]. Check for non read-only path with [statvfs(), statfs(), getfsstat()] * Fix Swiftlint build error due to the identifier_name rule * #6040 #6041 - Fix xcode 14.x is not compatible with 13.4.1 build, due to FailedChecks not conforming to CaseIterable * Revert "#6040 #6041 - Fix xcode 14.x is not compatible with 13.4.1 build, due to FailedChecks not conforming to CaseIterable" This reverts commit 319e9a0. * Update README.md * UIApplication.shared.canOpenURL() background thread change * Update IOSSecuritySuite.podspec * let's play a game with the Shadow's dev <haha> * 1.9.9 * iASE promotion * Update README.md * Improve checkDYLD performance By optimizing the case insensitive comparison. * Use set for storing suspicious libraries * Update README.md (removed Swiftshield) * Update README.md * Update IOSSecuritySuite.podspec * Update README.md * Update README.md * Improve code style * Fix many swiftlint issues * bug fixes after last PR * Swiftlint + Xcode 15 compatibility support * Update RuntimeHookChecker.swift * Update FrameworkClientApp.xcscheme * Update IOSSecuritySuite.xcscheme * fix for securing/issues/107 * 1.9.11 * nslog -> print * fix for securing/issues/106 * add ios privacy manifest * Removed obsolete `LSApplicationQueriesSchemes` from README.md. * lockdown mode detector * Update README.md * new EULA license * Update README.md * Update README.md * Update IOSSecuritySuite.podspec * Update README.md * typo fix * Update IOSSecuritySuite.podspec * search symbols from `__DATA_CONST` segment * check protection before writing * Fix missing PrivacyInfo.xcprivacy in xcodeproj * Fix missing PrivacyInfo.xcprivacy : Update swift-tools to 5.3 to allow resources defintion in targets Fix missing PrivacyInfo.xcprivacy when building framework using Xcode Package Dependencies. * Fix missing PrivacyInfo.xcprivacy : Move top root Resources folder inside target folder Fix missing PrivacyInfo.xcprivacy when building framework using Xcode Package Dependencies. - Resources folder must be part of a target folder hierarchy * Fix missing PrivacyInfo.xcprivacy : Add resources to target definition Fix missing PrivacyInfo.xcprivacy when building framework using Xcode Package Dependencies. * Update IOSSecuritySuite.podspec * fix podspec * Dopamine hide-jailbreak detector * VPN detection added * 2.1.0 docs update --------- Co-authored-by: Wojciech Reguła <[email protected]> Co-authored-by: Mario Sepulveda <[email protected]> Co-authored-by: Matěj Kašpar Jirásek <[email protected]> Co-authored-by: Izabella Melo <[email protected]> Co-authored-by: longxiang.guo <[email protected]> Co-authored-by: Lippmann, Erik <[email protected]> Co-authored-by: p-x9 <[email protected]> Co-authored-by: Blazej SLEBODA <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We seem to be seeing a jump in our jailbreak detections related to "activator://" URL scheme detected.
These devices seem to be legitimate and not jailbroken, I'm wondering if anybody else is seeing this? and should we remove this check?
Our app is UK based and we're I'm wondering if there is an app on AppStore that has registered this URL which is causing the false detections.
The text was updated successfully, but these errors were encountered: