用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill t0839-module-firmware命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
正在显示 SKILL.md
基于 SOC 职业分类
| name | T0839_module-firmware |
| description | Adversaries may install malicious or vulnerable firmware onto modular hardware devices. |
| category | configuration |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","ics","t0839","persistence","impair-process-control"] |
| technique_id | T0839 |
| tactic | persistence |
| all_tactics | ["persistence","impair-process-control"] |
| platforms | ["ICS"] |
| mitre_url | https://attack.mitre.org/techniques/T0839 |
| tech_stack | ["ics"] |
| cwe_ids | ["CWE-276"] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Adversaries may install malicious or vulnerable firmware onto modular hardware devices. Control system devices often contain modular hardware devices. These devices may have their own set of firmware that is separate from the firmware of the main control system equipment.
This technique is similar to System Firmware, but is conducted on other system components that may not have the same capabilities or level of integrity checking. Although it results in a device re-image, malicious device firmware may provide persistent access to remaining devices.
An easy point of access for an adversary is the Ethernet card, which may have its own CPU, RAM, and operating system. The adversary may attack and likely exploit the computer on an Ethernet card. Exploitation of the Ethernet card computer may enable the adversary to accomplish additional attacks, such as the following:
Platforms: ICS
Determine if the target ICS/SCADA environment is susceptible to Module Firmware by examining operational technology systems and network architecture.
Review whether mitigations for T0839 are in place. If defenses are absent or misconfigured, this technique may be exploitable in the ICS environment.
The encryption of firmware should be considered to prevent adversaries from identifying possible vulnerabilities within the firmware.
Check the integrity of the existing BIOS or EFI to determine if it is vulnerable to modification. Use Trusted Platform Module technology. Move system's root of trust to hardware to prevent tampering with the SPI flash memory. Technologies such as Intel Boot Guard can assist with this.
Authenticate connections fromsoftware and devices to prevent unauthorized systems from accessing protected management functions.
Filter for protocols and payloads associated with firmware activation or updating activity.
The encryption of firmware should be considered to prevent adversaries from identifying possible vulnerabilities within the firmware.
Devices should verify that firmware has been properly signed by the vendor before allowing installation.
Perform integrity checks of firmware before uploading it on a device. Utilize cryptographic hashes to verify the firmware has not been tampered with by comparing it to a trusted hash of the firmware. This could be from trusted data sources (e.g., vendor site) or through a third-party verification service.
Protocols used for device management should authenticate all network messages to prevent unauthorized system changes.
Devices that allow remote management of firmware should require authentication before allowing any changes. The authentication mechanisms should also support Account Use Policies, Password Policies, and User Account Management.
Segment operational network and systems to restrict access to critical system functions to predetermined management systems.
All devices or systems changes, including all administrative functions, should require authentication. Consider using access management technologies to enforce authorization on all management interface access attempts, especially when the device does not inherently provide strong authentication and authorization functions.
Use host-based allowlists to prevent devices from accepting connections from unauthorized systems. For example, allowlists can be used to ensure devices can only connect with master stations or known management/engineering workstations.
| Finding | Severity | Impact |
|---|---|---|
| Module Firmware technique applicable | High | Persistence |
| CWE ID | Title |
|---|---|
| CWE-276 | Incorrect Default Permissions |