READ_CALL_LOG
Returns call history, which the mprivhaan payload exfiltrates as a social graph plus timing data that becomes leverage for the next stage of social engineering.
Runtime prompt. READ_CALL_LOG returns full call history: who was called, when, for how long, and whether the call was missed or answered.
The write-up traces the exact query. DataSyncHelper reads CallLog.Calls.CONTENT_URI for _id, number, name, type, date, duration, sorted by date with limit and offset pagination, and the triple worker chain (CallLogPollingWorker, the upload worker, and the retry worker) exfiltrates the result. The pagination matters practically: a long call history does not fit in one request, so the sweeper has to walk it in pages, and any page that fails is replayed by the retry worker.
What comes out the other end is a social graph plus timing patterns, which is a more precise description than it first appears. The names alone are a contact list. The dates and durations are behavioural: who gets called regularly, who only at month end, which relationships are close enough to call often, and which contacts are institutions rather than people. Banks, family, employers.
That is leverage for the next stage of social engineering rather than an end in itself. An operator who knows a victim's bank calls on a schedule can time a follow-up call or a fake alert to land when the real one is expected.
Related: READ_PHONE_STATE, READ_CONTACTS, CALL_PHONE
Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.