2025, the year of the Infostealer #1735
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
dscl -authonlypassword validation +sudo -Sreuse andxattr -cquarantine removal🎯 Content Summary
Pentest Partners describes why infostealers accelerated in 2025 (fastest-growing malware category) and provides a DFIR walk-through of a real macOS infostealer intrusion that succeeded in collecting and staging data but failed to exfiltrate due to network egress controls.
1) Why infostealers scaled in 2025 (tradecraft vs. CVEs)
The post highlights that these intrusions commonly do not require memory corruption or a CVE: the primary “exploit” is user-driven execution (s...
🔧 Technical Details
User-execution initial access (no CVE): deliver a “normal-looking” terminal one-liner (installer/bootstrapper) via a lookalike site (e.g., spoofed Homebrew) and force a UI “Copy” button so victims can’t manually inspect the full pasted text; append hidden payload logic such as a base64-encoded command after the legitimate-looking command to trigger stage-1 execution.
macOS password capture + validation trick: repeatedly prompt for the user’s password and validate correctness locally with
dscl . -authonly ...; once validated, save it (e.g.,/tmp/.pass) and reuse it for non-interactive privileged actions withsudo -S(password via stdin), enabling follow-on steps like clearing quarantine attributes (xattr -c <file>), permission changes (chmod +x), execution of a downloaded stage, and installation of system-wide persistence.Anti-sandbox evasion: query host hardware/memory with
system_profiler</...🤖 Agent Actions
Summary:
Tests:
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.