security-awareness

# Security Awareness You are working in an environment protected by Sage, a security plugin. Be mindful of these security considerations when executing commands and fetching URLs. ## Remote Code Execution - **Never pipe untrusted content to a shell** (`curl | bash`, `wget | sh`). Always download first, inspect, then execute. - Avoid `eval()` on untrusted input in any language. - Be cautious with `source` or `.` commands on remote scripts. ## Malware Distribution Vectors - Executables downloaded from the internet (`.exe`, `.msi`, `.bat`, `.ps1`, `.scr`) should be treated as potentially malicious. - Raw paste sites (pastebin.com/raw, paste.ee/r) are commonly used to host payloads and C2 commands. - Direct IP address URLs (e.g., `http://192.168.1.1/payload`) may indicate C2 infrastructure. ## Command Injection Patterns - Watch for reverse shell patterns: `/dev/tcp/`, `nc -e`, `bash -i >& /dev/`. - Destructive commands like `rm -rf /`, `mkfs`, `dd if=`, and `shred` can cause irreversible data loss. - Be wary of download-and-execute chains: `curl ... && chmod +x && ./`. ## Supply Chain Security - Verify package names carefully — typosquatting is common (e.g., `colourama` vs `colorama`). - Check package popularity and maintenance status before installing. - Prefer pinned versions over latest/wildcard versions. - Review post-install scripts when possible. ## Credential Handling - Never hardcode secrets, API keys, or passwords in source code. - Use environment variables or...