This is a defensive tool-intelligence page. It is intended for analyst navigation, source review, and hunt planning. It is not a malware-analysis report and does not contain sample code or binaries.
Summary
- Associated actor(s): APT42
- Tool type(s): Script / collection tool
- Confidence level(s): Medium
- Source ID(s):
SRC-MITRE-G1044
Behavior
| Actor | Behavior Summary |
|---|
| APT42 | PowerShell-based collection tooling referenced for APT42 activity; useful as a behavior anchor for script execution and collection staging. |
Hash And IOC Status
| Actor | Status | Reference |
|---|
| APT42 | Hash not committed; source-linked behavior only. | SRC-MITRE-G1044 |
Hashes and IOCs on this page are source pointers or representative public indicators. They SHOULD be refreshed from the linked source before operational use and MUST NOT be used alone for actor attribution.
Defensive Hunting Notes
| Actor | Hunting Notes |
|---|
| APT42 | Hunt PowerShell collection from unusual parent processes, cloud identity follow-on access, and archive staging after phishing. |
Handling Notes
| Actor | Handling Notes |
|---|
| APT42 | Do not store script content or samples. |
Crosslinks
Mapped ATT&CK Techniques For Associated Actor(s)
| Actor | Technique | Tactic | Mapping Quality | Source |
|---|
| APT42 | T1530 Data from Cloud Storage | Collection | M1 | SRC-MITRE-G1044 |
| APT42 | T1102 Web Service | Command and Control | M1 | SRC-MITRE-G1044 |
| APT42 | T1566.002 Spearphishing Link | Initial Access | M3 | SRC-GOOGLE-APT42-PHISHING |
These detections are mapped through the associated actor or scenario and are not automatically tool-specific. Promote a tool-specific detection only after the behavior is tied to telemetry and test evidence.
These hunts are mapped through the associated actor or scenario and may need narrowing before they are used for this specific tool.
Source Review
| Source | Publisher | Date | Reliability | Type | Last Reviewed |
|---|
SRC-MITRE-G1044 | MITRE ATT&CK | 2026-05-13 | A | Knowledge base | 2026-05-14 |
If a source publishes a large or frequently changing IOC appendix, keep the current IOC list in the source system or TIP and store only the pointer here.