القائمة
Adversaries may establish persistence by modifying RC scripts, which are executed during a Unix-like system’s startup.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill t1037-004-rc-scriptsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | T1037.004_rc-scripts |
| description | Adversaries may establish persistence by modifying RC scripts, which are executed during a Unix-like system’s startup. |
| category | configuration |
| version | 18.1 |
| author | cyberstrike-official |
| tags | ["mitre-attack","enterprise","t1037.004","persistence","privilege-escalation","macos","linux","network-devices","esxi","sub-technique"] |
| technique_id | T1037.004 |
| tactic | persistence |
| all_tactics | ["persistence","privilege-escalation"] |
| platforms | ["macOS","Linux","Network Devices","ESXi"] |
| mitre_url | https://attack.mitre.org/techniques/T1037/004 |
| tech_stack | ["macos","linux","network devices","esxi"] |
| cwe_ids | ["CWE-276"] |
| chains_with | ["T1037","T1037.001","T1037.002","T1037.003","T1037.005"] |
| prerequisites | ["T1037"] |
| severity_boost | {"T1037":"Chain with T1037 for deeper attack path","T1037.001":"Chain with T1037.001 for deeper attack path","T1037.002":"Chain with T1037.002 for deeper attack path"} |
Sub-technique of: T1037
Adversaries may establish persistence by modifying RC scripts, which are executed during a Unix-like system’s startup. These files allow system administrators to map and start custom services at startup for different run levels. RC scripts require root privileges to modify.
Adversaries may establish persistence by adding a malicious binary path or shell commands to rc.local, rc.common, and other RC scripts specific to the Unix-like distribution. Upon reboot, the system executes the script's contents as root, resulting in persistence.
Adversary abuse of RC scripts is especially effective for lightweight Unix-like distributions using the root user as default, such as ESXi hypervisors, IoT, or embedded systems. As ESXi servers store most system files in memory and therefore discard changes on shutdown, leveraging /etc/rc.local.d/local.sh is one of the few mechanisms for enabling persistence across reboots.
Several Unix-like systems have moved to Systemd and deprecated the use of RC scripts. This is now a deprecated mechanism in macOS in favor of Launchd. This technique can be used on Mac OS X Panther v10.3 and earlier versions which still execute the RC scripts. To maintain backwards compatibility some systems, such as Ubuntu, will execute the RC scripts if they exist with the correct file permissions.
Platforms: macOS, Linux, Network Devices, ESXi
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
Modify rc.common
Supported Platforms: macos Elevation Required: Yes
sudo echo osascript -e 'tell app "Finder" to display dialog "Hello World"' >> /etc/rc.common
Modify rc.common
Supported Platforms: linux Elevation Required: Yes
filename='/etc/rc.common';if [ ! -f $filename ];then sudo touch $filename;else sudo cp $filename /etc/rc.common.original;fi
printf '%s\n' '#!/bin/bash' | sudo tee /etc/rc.common
echo "python3 -c \"import os, base64;exec(base64.b64decode('aW1wb3J0IG9zCm9zLnBvcGVuKCdlY2hvIGF0b21pYyB0ZXN0IGZvciBtb2RpZnlpbmcgcmMuY29tbW9uID4gL3RtcC9UMTAzNy4wMDQucmMuY29tbW9uJykK'))\"" | sudo tee -a /etc/rc.common
printf '%s\n' 'exit 0' | sudo tee -a /etc/rc.common
sudo chmod +x /etc/rc.common
Modify rc.local
Supported Platforms: linux Elevation Required: Yes
filename='/etc/rc.local';if [ ! -f $filename ];then sudo touch $filename;else sudo cp $filename /etc/rc.local.original;fi
[ "$(uname)" = 'FreeBSD' ] && alias python3=python3.9 && printf '#\!/usr/local/bin/bash' | sudo tee /etc/rc.local || printf '#!/bin/bash' | sudo tee /etc/rc.local
echo "\npython3 -c \"import os, base64;exec(base64.b64decode('aW1wb3J0IG9zCm9zLnBvcGVuKCdlY2hvIGF0b21pYyB0ZXN0IGZvciBtb2RpZnlpbmcgcmMubG9jYWwgPiAvdG1wL1QxMDM3LjAwNC5yYy5sb2NhbCcpCgo='))\"" | sudo tee -a /etc/rc.local
printf 'exit 0' | sudo tee -a /etc/rc.local
sudo chmod +x /etc/rc.local
If Atomic Red Team tests are not applicable, manually verify the technique by:
Identify Attack Surface: Determine if the target environment is susceptible to RC Scripts by examining the target platforms (macOS, Linux, Network Devices).
Assess Existing Defenses: Review whether mitigations for T1037.004 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Limit privileges of user accounts so only authorized users can edit the rc.common file.
| Finding | Severity | Impact |
|---|---|---|
| RC Scripts technique applicable | High | Persistence |
| CWE ID | Title |
|---|---|
| CWE-276 | Incorrect Default Permissions |