Analyzing Supply Chain Malware Artifacts
Overview
Supply chain attacks compromise legitimate software distribution channels to deliver malware through trusted update mechanisms. Notable examples include SolarWinds SUNBURST (2020, affecting 18,000+ customers), 3CX SmoothOperator (2023, a cascading supply chain attack originating from Trading Technologies), and numerous npm/PyPI package poisoning campaigns. Analysis involves comparing trojanized binaries against legitimate versions, identifying injected code in build artifacts, examining code signing anomalies, and tracing the infection chain from initial compromise through payload delivery. As of 2025, supply chain attacks account for 30% of all breaches, a 100% increase from prior years.
When to Use
- When investigating security incidents that require analyzing supply chain malware artifacts
- When building detection rules or threat hunting queries for this domain
- When SOC analysts need structured procedures for this analysis type
- When validating security monitoring coverage for related attack techniques
Prerequisites
- Python 3.9+ with
pefile, ssdeep, hashlib
- Binary diff tools (BinDiff, Diaphora)
- Code signing verification tools (sigcheck, codesign)
- Software composition analysis (SCA) tools
- Access to legitimate software versions for comparison
- Package repository monitoring (npm, PyPI, NuGet)
Workflow
Step 1: Binary Comparison Analysis
#!/usr/bin/env python3
"""Compare trojanized binary against legitimate version."""
import hashlib
import pefile
import sys
import json
def compare_pe_files(legitimate_path, suspect_path):
"""Compare PE file structures between legitimate and suspect versions."""
legit_pe = pefile.PE(legitimate_path)
suspect_pe = pefile.PE(suspect_path)
report = {"differences": [], "suspicious_sections": [], "import_changes": []}
# Compare sections
legit_sections = {s.Name.rstrip(b'\x00').decode(): {
"size": s.SizeOfRawData,
"entropy": s.get_entropy(),
"characteristics": s.Characteristics,
} for s in legit_pe.sections}
suspect_sections = {s.Name.rstrip(b'\x00').decode(): {
"size": s.SizeOfRawData,
"entropy": s.get_entropy(),
"characteristics": s.Characteristics,
} for s in suspect_pe.sections}
# Find new or modified sections
for name, props in suspect_sections.items():
if name not in legit_sections:
report["suspicious_sections"].append({
"name": name, "reason": "New section not in legitimate version",
"size": props["size"], "entropy": round(props["entropy"], 2),
})
elif abs(props["size"] - legit_sections[name]["size"]) > 1024:
report["suspicious_sections"].append({
"name": name, "reason": "Section size significantly changed",
"legit_size": legit_sections[name]["size"],
"suspect_size": props["size"],
})
# Compare imports
legit_imports = set()
if hasattr(legit_pe, 'DIRECTORY_ENTRY_IMPORT'):
for entry in legit_pe.DIRECTORY_ENTRY_IMPORT:
for imp in entry.imports:
if imp.name:
legit_imports.add(f"{entry.dll.decode()}!{imp.name.decode()}")
suspect_imports = set()
if hasattr(suspect_pe, 'DIRECTORY_ENTRY_IMPORT'):
for entry in suspect_pe.DIRECTORY_ENTRY_IMPORT:
for imp in entry.imports:
if imp.name:
suspect_imports.add(f"{entry.dll.decode()}!{imp.name.decode()}")
new_imports = suspect_imports - legit_imports
if new_imports:
report["import_changes"] = list(new_imports)
# Check code signing
report["legit_signed"] = bool(legit_pe.OPTIONAL_HEADER.DATA_DIRECTORY[4].Size)
report["suspect_signed"] = bool(suspect_pe.OPTIONAL_HEADER.DATA_DIRECTORY[4].Size)
return report
def hash_file(filepath):
"""Calculate multiple hashes for a file."""
hashes = {}
with open(filepath, 'rb') as f:
data = f.read()
for algo in ['md5', 'sha1', 'sha256']:
h = hashlib.new(algo)
h.update(data)
hashes[algo] = h.hexdigest()
return hashes
if __name__ == "__main__":
if len(sys.argv) < 3:
print(f"Usage: {sys.argv[0]} <legitimate_binary> <suspect_binary>")
sys.exit(1)
report = compare_pe_files(sys.argv[1], sys.argv[2])
print(json.dumps(report, indent=2))
Validation Criteria
- Trojanized components identified through binary diffing
- Injected code isolated and analyzed separately
- Code signing anomalies documented
- Infection timeline reconstructed from build artifacts
- Downstream impact scope assessed across affected systems
- IOCs extracted for detection and blocking
References
1---2name: analyzing-supply-chain-malware-artifacts-23description: Investigate supply chain attack artifacts including trojanized software4 updates, compromised build pipelines, and sideloaded dependencies to identify intrusion5 vectors and scope of compromise.6domain: cybersecurity7subdomain: malware-analysis8tags:9- supply-chain10- malware-analysis11- trojanized-software12- solarwinds13- 3cx14- dependency-confusion15- software-integrity16version: '1.0'17author: mahipal18license: Apache-2.019atlas_techniques:20- AML.T001021nist_ai_rmf:22- GOVERN-5.223- MAP-1.624- MANAGE-2.225d3fend_techniques:26- Platform Hardening27- Hardware Component Inventory28- Restore Object29- Electromagnetic Radiation Hardening30- RF Shielding31nist_csf:32- DE.AE-0233- RS.AN-0334- ID.RA-0135- DE.CM-0136mitre_attack:37- T1195.00238- T1195.00139- T155440- T1553.00241- T102742metadata:43 source: https://skillmd.com/skills/26zl/analyzing-supply-chain-malware-artifacts-244---4546# Analyzing Supply Chain Malware Artifacts4748## Overview4950Supply chain attacks compromise legitimate software distribution channels to deliver malware through trusted update mechanisms. Notable examples include SolarWinds SUNBURST (2020, affecting 18,000+ customers), 3CX SmoothOperator (2023, a cascading supply chain attack originating from Trading Technologies), and numerous npm/PyPI package poisoning campaigns. Analysis involves comparing trojanized binaries against legitimate versions, identifying injected code in build artifacts, examining code signing anomalies, and tracing the infection chain from initial compromise through payload delivery. As of 2025, supply chain attacks account for 30% of all breaches, a 100% increase from prior years.515253## When to Use5455- When investigating security incidents that require analyzing supply chain malware artifacts56- When building detection rules or threat hunting queries for this domain57- When SOC analysts need structured procedures for this analysis type58- When validating security monitoring coverage for related attack techniques5960## Prerequisites6162- Python 3.9+ with `pefile`, `ssdeep`, `hashlib`63- Binary diff tools (BinDiff, Diaphora)64- Code signing verification tools (sigcheck, codesign)65- Software composition analysis (SCA) tools66- Access to legitimate software versions for comparison67- Package repository monitoring (npm, PyPI, NuGet)6869## Workflow7071### Step 1: Binary Comparison Analysis7273```python74#!/usr/bin/env python375"""Compare trojanized binary against legitimate version."""76import hashlib77import pefile78import sys79import json808182def compare_pe_files(legitimate_path, suspect_path):83 """Compare PE file structures between legitimate and suspect versions."""84 legit_pe = pefile.PE(legitimate_path)85 suspect_pe = pefile.PE(suspect_path)8687 report = {"differences": [], "suspicious_sections": [], "import_changes": []}8889 # Compare sections90 legit_sections = {s.Name.rstrip(b'\x00').decode(): {91 "size": s.SizeOfRawData,92 "entropy": s.get_entropy(),93 "characteristics": s.Characteristics,94 } for s in legit_pe.sections}9596 suspect_sections = {s.Name.rstrip(b'\x00').decode(): {97 "size": s.SizeOfRawData,98 "entropy": s.get_entropy(),99 "characteristics": s.Characteristics,100 } for s in suspect_pe.sections}101102 # Find new or modified sections103 for name, props in suspect_sections.items():104 if name not in legit_sections:105 report["suspicious_sections"].append({106 "name": name, "reason": "New section not in legitimate version",107 "size": props["size"], "entropy": round(props["entropy"], 2),108 })109 elif abs(props["size"] - legit_sections[name]["size"]) > 1024:110 report["suspicious_sections"].append({111 "name": name, "reason": "Section size significantly changed",112 "legit_size": legit_sections[name]["size"],113 "suspect_size": props["size"],114 })115116 # Compare imports117 legit_imports = set()118 if hasattr(legit_pe, 'DIRECTORY_ENTRY_IMPORT'):119 for entry in legit_pe.DIRECTORY_ENTRY_IMPORT:120 for imp in entry.imports:121 if imp.name:122 legit_imports.add(f"{entry.dll.decode()}!{imp.name.decode()}")123124 suspect_imports = set()125 if hasattr(suspect_pe, 'DIRECTORY_ENTRY_IMPORT'):126 for entry in suspect_pe.DIRECTORY_ENTRY_IMPORT:127 for imp in entry.imports:128 if imp.name:129 suspect_imports.add(f"{entry.dll.decode()}!{imp.name.decode()}")130131 new_imports = suspect_imports - legit_imports132 if new_imports:133 report["import_changes"] = list(new_imports)134135 # Check code signing136 report["legit_signed"] = bool(legit_pe.OPTIONAL_HEADER.DATA_DIRECTORY[4].Size)137 report["suspect_signed"] = bool(suspect_pe.OPTIONAL_HEADER.DATA_DIRECTORY[4].Size)138139 return report140141142def hash_file(filepath):143 """Calculate multiple hashes for a file."""144 hashes = {}145 with open(filepath, 'rb') as f:146 data = f.read()147 for algo in ['md5', 'sha1', 'sha256']:148 h = hashlib.new(algo)149 h.update(data)150 hashes[algo] = h.hexdigest()151 return hashes152153154if __name__ == "__main__":155 if len(sys.argv) < 3:156 print(f"Usage: {sys.argv[0]} <legitimate_binary> <suspect_binary>")157 sys.exit(1)158 report = compare_pe_files(sys.argv[1], sys.argv[2])159 print(json.dumps(report, indent=2))160```161162## Validation Criteria163164- Trojanized components identified through binary diffing165- Injected code isolated and analyzed separately166- Code signing anomalies documented167- Infection timeline reconstructed from build artifacts168- Downstream impact scope assessed across affected systems169- IOCs extracted for detection and blocking170171## References172173- [ReversingLabs - 3CX Supply Chain Analysis](https://www.reversinglabs.com/blog/what-went-wrong-with-the-3cx-software-supply-chain-attack-and-how-it-could-have-been-prevented)174- [Fortinet - SolarWinds Supply Chain Attack](https://www.fortinet.com/resources/cyberglossary/solarwinds-cyber-attack)175- [Picus - 3CX SmoothOperator Analysis](https://www.picussecurity.com/resource/blog/smoothoperator-analysis-of-3cxdesktopapp-supply-chain-attack)176- [MITRE ATT&CK T1195 - Supply Chain Compromise](https://attack.mitre.org/techniques/T1195/)