Skip to content

Security & malwareDevice & system

iOS Crash Logs and JetsamEvent Reports (.ips)

iOS diagnostic reports in .ips files: app and system crashes, JetsamEvent memory reports listing running processes, where to collect them and how to read them.

Location
/private/var/mobile/Library/Logs/CrashReporter/ (*.ips, Retired/); also crashes_and_spins/ in a sysdiagnose and Settings > Privacy & Security > Analytics Data
Evidence area
Proves
Which apps and system processes crashed, hung or were killed, when, on which OS build, and (in JetsamEvent reports) which processes were resident in memory at the time
Timestamps
Local time with UTC offset in the JSON metadata line (timestamp) and in body fields such as captureTime; convert to UTC
Acquisition
An unlocked, trusted device through the crash report service (no backup needed), a sysdiagnose, or a full file system extraction
Retention
iOS keeps a limited number of reports per type and moves older ones to Retired/ before deleting them; weeks is typical. Collect early
Collection
idevicecrashreport, pymobiledevice3 crash pull, sysdiagnose, Full file system extraction

What it is

iOS writes a diagnostic report when something goes wrong or needs to be measured: an app crash, a hang, a CPU or disk resource violation, or a memory pressure event. Reports use the .ips format: a first line of JSON metadata (name, bug type, build, timestamp, incident ID), followed by the body, which is JSON for modern crash reports and text for some other kinds.

Two report families matter most in investigations:

  • Crash reports (bug_type 309 with a JSON body, 109 for the older text form): which process crashed, when, the exception type and the stack. Exploits that fail often crash a system process, which is why crash reports are part of spyware triage.
  • JetsamEvent reports: written when iOS kills processes to reclaim memory. They list the processes resident in memory at that moment, with names and states, which gives a snapshot of what was running, including daemons that never appear in the app list.

Where it lives

SourcePathNotes
Full file system/private/var/mobile/Library/Logs/CrashReporter/*.ipsCurrent reports
Full file system.../CrashReporter/Retired/Older reports awaiting deletion
Crash report servicePulled from a trusted, unlocked deviceidevicecrashreport or pymobiledevice3 crash pull
sysdiagnosecrashes_and_spins/ and related foldersReports present when the sysdiagnose was taken
On deviceSettings > Privacy & Security > Analytics & Improvements > Analytics DataViewable and shareable one by one

The crash report service moves reports off the device by default in some tools: use the option that copies without deleting, and document it.

What it proves

  • A process (by name, path and bundle ID) crashed or was terminated at a given time, on a given OS build and app version.
  • The exception type, termination reason and faulting thread, which can point to exploitation attempts or instability.
  • For JetsamEvent reports, the set of processes in memory, their sizes and states at the time of the event.
  • Analytics summaries (for example bug_type 225 reports) with app install, launch, crash counts and foreground duration over a period, where present.

A crash is not proof of attack. Most crashes are bugs. What matters is the combination of process, time and context.

Key fields

LocationFieldMeaning
Metadata linename, bundleID, app_versionProcess and app
Metadata linebug_typeReport kind (309 crash, 288 stackshot, others exist)
Metadata linetimestamp, os_version, incident_idReport time, build, unique ID
Crash bodyprocName, procPath, pid, procLaunch, captureTimeProcess, launch and crash times
Crash bodyexception, termination, faultingThreadWhy it crashed
JetsamEvent bodyprocesses[] with name, pid, states, rpagesResident processes
JetsamEvent bodylargestProcessProcess holding the most memory

Apple documents the JSON crash format in "Interpreting the JSON format of a crash report". Other report kinds are undocumented and change between releases.

Timestamps

Report times are local time with an explicit UTC offset, for example 2026-09-12 21:04:17.00 +0200. Convert to UTC using the offset in the value, not the examiner's time zone.

head -1 JetsamEvent-2026-09-12-210417.ips | python3 -m json.tool

The file name also carries the local date and time of the report.

Retention

iOS caps the number of reports it keeps per type and ages older ones through Retired/. Expect weeks rather than months, and less on busy devices. Sending reports to Apple does not delete them locally, but tools and users can. Collect at the start of an examination.

Collection

  • On an unlocked, trusted device: pymobiledevice3 crash pull ./case/crash or idevicecrashreport -k ./case/crash (-k keeps the reports on the device).
  • Generate a sysdiagnose for the same content plus logs.
  • From a full file system, collect CrashReporter including Retired.

Parsing

  • iLEAPP lists all .ips reports, parses crash reports (types 309 and 109) and analytics summaries.
  • MVT parses analytics data in file system mode and matches process names against indicator files.
  • The EC-DIGIT-CSIRC sysdiagnose analyser parses crash reports inside a sysdiagnose.
  • For a single report, a JSON viewer and the Apple documentation are enough.

Investigator tips

  • Look for crashes of messaging and media parsing processes (for example imagent, IMTranscoderAgent, MessagesBlastDoorService, mediaserverd) clustered around a date of interest. Several zero-click exploit chains have targeted this attack surface, but crashes there are also common after ordinary bugs.
  • JetsamEvent process lists can reveal a process name that also appears in DataUsage or shutdown.log. Independent sources agreeing is what makes a lead strong.
  • A crash report proves the app existed on that date, which helps when the app has since been deleted (see installed apps).
  • The spyware triage guide puts crash reports in context with the other indicators.

See also