Can I trust Meross?
This app did not meet two or more trust checks, has a critical issue in one, or has a red flag.
- What it means for you
- Device commands route through the local network or Apple's end-to-end encrypted infrastructure, not through Meross servers. Account credentials are stored in the device's secure Keychain. The build includes code to send usage and crash data to Firebase Analytics, Firebase Crashlytics, and AWS services. No advertising network has access to usage data.
- Main concern
- Home WiFi password exposed via hardcoded AES IV during device provisioning
- The developer's description
- Smart home controller for Meross IoT devices. Manage smart plugs, switches, hubs, lights, and automations. Control locally or remotely via cloud with scene and schedule support.
- Third-party services
- 10
- Findings rated low or higher
- 4
Open on the App StoreOpens the app's listing on the App Store in a new tab.
Full findings
Open this scan in your dashboardThe account that ran this scan sees every finding and the Rescan button there.
Trust checks
Secure by Design
One criterion not metSecurity gaps detected
Why this result
This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.
Data Minimization
One criterion not metTracking lacks clear disclosure
Why this result
This build contains analytics or attribution code written to send data to companies other than the developer. No consent step was found before that code runs, and the app's disclosures do not describe the collection in full. Tracking by itself is ordinary; what this check reports is the combination of collection, recipient and absent disclosure.
Manifest Mismatch
One criterion not metDisclosure incomplete or contradicted
Why this result
The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.
User Control
StrongNo lock-in
Why this result
The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.
The app supports the Matter smart home standard, an open protocol designed to let compatible devices be used on other platforms without proprietary restrictions. No artificial barriers to switching services or exporting user data were found.
Strengths
- Matter and HomeKit device command code addresses the local network or Apple's end-to-end encrypted infrastructure; no code was found to send them through Meross cloud servers
- Cloud connections to Meross backends use certificate pinning on top of standard TLS chain validation
- Account credentials, authentication tokens, and device certificates are stored in the iOS Keychain — not in files, NSUserDefaults, or CoreData
- App Group access is restricted to the developer's own first-party extensions under Team ID 7EBFRDSKEJ; no third-party developer can access the shared App Group
- External web links are sandboxed in SFSafariViewController with no access to the app's cookies or storage
- WebView has no JavaScript bridge — injected web content cannot reach native device APIs
- Stack canaries are active throughout the binary (5,389 callers of ___stack_chk_fail), providing memory corruption defense
- No advertising SDK present — no broad-reach ad network has access to usage data
What the app contains
10 services
Third-party services the scan names in the build:
- Firebase Analytics
- Firebase Crashlytics
- Firebase Messaging
- AWS Amplify
- AWS Cognito
- AWS S3
- OpenTelemetry Swift
- Kookong SDK
- OpenWeatherMap API
- ipinfo.io
Libraries
| Library | Version | Advisory |
|---|---|---|
| intellect_socket | not recorded | none confirmed |
Method and limits
Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.
- Files decompiled
- 180,206
- Scan date
- 22 August 2026
Corrections
No correction is published for this app.
Developer response
No response is published for this app.
Report an error Opens an email to [email protected] that names this app and this scan.