Loan-App Harassment: Nine Days From Panic to Remediation

1. Summary

Someone who had applied for two consumer loans contacted me in distress: repeated refusals, then immediate harassment calls from foreign numbers, unknown applications on her handset, and a fear that her identity had been taken. Over nine days I audited the device over ADB, identified seven sideloaded packages, reconstructed what each one could access, guided remediation, and packaged the evidence for a cybercrime complaint.

The finding that mattered was not exotic malware. It was a permission model: a handset that had been persuaded to grant contacts, SMS and storage access to applications installed from outside the store, and a lender ecosystem in which that address book is the collection mechanism.

2. Context

3. What the parties saw

  1. Two loan applications were declined; no money was disbursed.
  2. Within days, calls arrived from foreign numbers, referencing people in her contact list by name.
  3. She noticed applications on the handset she did not remember installing.
  4. Messages escalated from reminders to threats of circulating photographs.

What was visible was harassment and unfamiliar icons. What was established afterwards was the mechanism: which packages were present, what permissions each held, and when they were installed.

4. Method

  1. Stabilise before investigating. Told her to stop installing anything, stop granting permissions, and keep the handset powered on and offline from unknown Wi-Fi.
  2. Inventory the device over ADB. adb shell pm list packages -3 for third-party packages, adb shell dumpsys package <pkg> for install time, installer and granted permissions, and a listing of /sdcard/Download/*.apk for the installers themselves.
  3. Map capability, not intent. For each package, record which dangerous permissions were granted: contacts, SMS, call log, storage, accessibility. Capability is what a reviewer can evidence; intent is what a headline claims.
  4. Preserve evidence before removal. Hash the APK files, screenshot the permission screens, export the call log and message headers with timestamps.
  5. Remediate in order. Revoke accessibility and device-admin grants first, then uninstall, then rotate credentials and enable 2FA on the accounts the apps could reach.
  6. Package for the complaint. One timeline, one evidence index, one plain-language narrative — the format a cybercrime portal accepts.

5. Evidence

ArtefactWhat it showsIntegrity
Package inventory (pm list packages -3)seven sideloaded packagesheld, hashed
Per-package dumpsys outputinstall times, installers, granted permissionsheld, hashed
APK files from /sdcard/Downloadinstallers retained on deviceheld, hashed
Call log and message headersharassment timeline from foreign numbersheld, redacted
Screenshots of permission screenswhat was granted, whenheld

APKs are not published. Identifiers are withheld and the victim is not named.

6. Findings

7. Indicators and red flags

8. What stopped it / what would have stopped it

9. Limitations

10. References


Disclaimer. This write-up describes a single documented instance and is published for professional education. All personal and institutional identifiers have been removed or replaced with synthetic values. Findings are limited to the evidence described above; nothing here should be read as an allegation against any named or unnamed party.