daily-security-triage

To detect shell profile injection and git config tampering, run an automated local security triage script. It scans shell profiles for suspicious eval, curl, wget, and python patterns, and checks .gitconfig for unusual core.hooksPath or suspicious aliases.

The best way to check for suspicious Node.js network connections is using an automated local security triage script. It utilizes lsof to identify unusual network connections originating from Node.js processes and detects unexpected global Node packages.

Yes, you can run a bash security triage script to find exposed secrets. It identifies exported API keys, tokens, and other secret environment variables configured within your shell profiles to help maintain local system integrity.

Yes, you need lsof installed to run these daily local security checks. The automated triage script requires bash, grep, and lsof utilities to successfully scan for suspicious network connections and verify system integrity.

An automated local security triage script checks ~/.node_modules for suspicious persistence. It detects unexpected global Node packages and identifies unusual network connections originating from Node.js processes to investigate potential system compromise.

You should run an automated local security triage script daily to proactively identify potential security issues before they escalate, or immediately use it when investigating a suspected system compromise to generate a summary report.