Has scraped runner process memory to extract short-lived identity tokens, which it then exchanged for per-package npm trusted-publisher tokens.1
- Tactic
- Credential Access
- Platform
- Linux
- Version
- 1.2
- Created
- 11 February 2020
- Last modified
- 24 October 2025
- Contributor
- Tim (Wadhwa-)Brown
Adversaries may gather credentials from the proc filesystem or /proc. The proc filesystem is a pseudo-filesystem used as an interface to kernel data structures for Linux based systems managing virtual memory. For each process, the /proc/<PID>/maps file shows how memory is mapped within the process’s virtual address space. And /proc/<PID>/mem, exposed for debugging purposes, provides access to the process’s virtual address space.[1][2]
Proc Filesystem MITRE reference T1003.007
5 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can scrape memory from the Runner.Worker process by reading /proc/<pid>/mem to extract secrets including plaintext tokens.123456
Has the ability to extract credentials from OS memory.1
Can use the <PID>/maps and <PID>/mem files to identify regex patterns to dump cleartext passwords from the browser's process memory.12
Can use the <PID>/maps and <PID>/mem file to search for regex patterns and dump the process memory.12
All 5 software entries for this technique
Offense vs defense T1003.007
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
Proc Filesystem detection strategy DET0593
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detecting OS Credential Dumping via /proc Filesystem Access on Linux
AN1631 · Linux
Monitoring adversary access to sensitive process memory via the /proc filesystem to extract credential material, often involving multi-step access to /proc/[pid]/mem or /proc/[pid]/maps combined with privilege escalation or credential scraping binaries.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | linux:Sysmon | EventCode=1 |
| Process AccessDC0035 | auditd:SYSCALL | ptrace or process_vm_readv |
| File AccessDC0055 | auditd:SYSCALL | open, read |
| File ModificationDC0061 | auditd:SYSCALL | write |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AccessedFilePath | Monitored paths such as /proc/[pid]/mem or /proc/[pid]/maps may need to be scoped based on environment |
| ProcessName | Command-line or binary names associated with credential scraping tools may vary |
| UserContext | Elevated user or unexpected user context accessing other process memory may indicate malicious activity |
| TimeWindow | Correlating memory access with process creation or ptrace activity within a specific time range |
Ensure that root accounts have complex, unique passwords across all systems on the network.
Follow best practices in restricting access to privileged accounts to avoid hostile programs from accessing sensitive information.
Tests from Atomic Red Team (MIT licence) · technique definition