Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Adversaries may attempt to get information about running processes on a device.
.claude/skills/cyberstrikeus-t1424-process-discovery/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | 25% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -53% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -25% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 41% | 0% |
Adversaries may attempt to get information about running processes on a device. Information obtained could be used to gain an understanding of common software/applications running on devices within a network. Adversaries may use the information from Process Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
Recent Android security enhancements have made it more difficult to obtain a list of running processes. On Android 7 and later, there is no way for an application to obtain the process list without abusing elevated privileges. This is due to the Android kernel utilizing the hidepid mount feature. Prior to Android 7, applications could utilize the ps command or examine the /proc directory on the device.
In iOS, applications have previously been able to use the sysctl command to obtain a list of running processes. This functionality has been removed in later iOS versions.
Platforms: Android, iOS
Determine if the target mobile environment is susceptible to Process Discovery by examining the target platforms (Android, iOS).
Review whether mitigations for T1424 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Android 7 and later iOS versions introduced changes that prevent applications from performing Process Discovery without elevated privileges.
Attestation can typically detect rooted devices. For MDM-enrolled devices, action can be taken if a device fails an attestation check.
| Finding | Severity | Impact | | -------------------------------------- | -------- | --------- | | Process Discovery technique applicable | High | Discovery |
| CWE ID | Title | | ------- | --------------------------------- | | CWE-200 | Exposure of Sensitive Information |
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 31,716 | 35,412 | +12% | 1 | 1 | 0% | 4,119 | 5,446 | +32% | 0 | 0 | — |
case-02 | fail→pass | 30,893 | 35,321 | +14% | 1 | 1 | 0% | 3,813 | 4,758 | +25% | 0 | 0 | — |
case-03 | fail→fail | 27,024 | 29,397 | +9% | 1 | 1 | 0% | 3,410 | 3,960 | +16% | 0 | 0 | — |
case-04 | pass→pass | 24,089 | 25,183 | +5% | 1 | 1 | 0% | 3,118 | 3,440 | +10% | 0 | 0 | — |
case-05 | pass→pass | 21,542 | 18,322 | -15% | 1 | 1 | 0% | 2,300 | 2,763 | +20% | 0 | 0 | — |
case-06 | fail→pass | 25,871 | 13,267 | -49% | 1 | 1 | 0% | 3,536 | 1,678 | -53% | 0 | 0 | — |
case-07 | fail→pass | 25,381 | 18,365 | -28% | 1 | 1 | 0% | 3,329 | 2,497 | -25% | 0 | 0 | — |
case-08 | fail→pass | 19,310 | 12,563 | -35% | 1 | 1 | 0% | 1,864 | 1,501 | -19% | 0 | 0 | — |
case-09 | pass→pass | 22,325 | 22,311 | -0% | 1 | 1 | 0% | 2,567 | 2,672 | +4% | 0 | 0 | — |
case-10 | pass→pass | 13,498 | 15,053 | +12% | 1 | 1 | 0% | 1,577 | 2,277 | +44% | 0 | 0 | — |
case-11 | pass→pass | 21,560 | 14,182 | -34% | 1 | 1 | 0% | 2,290 | 3,004 | +31% | 0 | 0 | — |
case-12 | pass→pass | 23,148 | 24,108 | +4% | 1 | 1 | 0% | 3,059 | 3,963 | +30% | 0 | 0 | — |
case-13 | fail→pass | 22,556 | 28,821 | +28% | 1 | 1 | 0% | 2,711 | 3,812 | +41% | 0 | 0 | — |
case-14 | pass→pass | 13,796 | 9,753 | -29% | 1 | 1 | 0% | 1,407 | 1,413 | +0% | 0 | 0 | — |
case-15 | fail→pass | 15,713 | 13,675 | -13% | 1 | 1 | 0% | 2,820 | 2,029 | -28% | 0 | 0 | — |
case-16 | pass→pass | 30,162 | 23,343 | -23% | 1 | 1 | 0% | 3,476 | 3,668 | +6% | 0 | 0 | — |
case-17 | pass→pass | 19,571 | 24,450 | +25% | 1 | 1 | 0% | 2,986 | 3,146 | +5% | 0 | 0 | — |
case-18 | fail→pass | 26,808 | 21,680 | -19% | 1 | 1 | 0% | 2,915 | 2,812 | -4% | 0 | 0 | — |
case-19 | pass→pass | 35,179 | 24,848 | -29% | 1 | 1 | 0% | 2,703 | 3,187 | +18% | 0 | 0 | — |
case-20 | pass→pass | 28,453 | 28,338 | -0% | 1 | 1 | 0% | 3,655 | 4,172 | +14% | 0 | 0 | — |
case-21 | pass→pass | 40,418 | 39,795 | -2% | 1 | 1 | 0% | 4,959 | 5,577 | +12% | 0 | 0 | — |
case-22 | pass→pass | 27,763 | 30,112 | +8% | 1 | 1 | 0% | 3,028 | 4,300 | +42% | 0 | 0 | — |
case-23 | pass→pass | 34,915 | 39,236 | +12% | 1 | 1 | 0% | 3,924 | 5,209 | +33% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +30 percentage points is the difference between those two pass rates over the 23 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.