linux-security-scanner@1.0.0
CAUTION· static onlyPublisher claims: "Linux security auditing tool that checks SSH configuration, open/listening ports, firewall rules (ufw/iptables/nftables), failed login attempts, sudoers perm..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-22 and scored it 59/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Privileged sudo command; Access to sensitive file paths; Privileged sudo command. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
echo "--- Users/groups with full sudo access ---"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.sudoers_perm=$(stat -c "%a" /etc/sudoers 2>/dev/null)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- Requires root/sudo for some checks (failed-logins reads /var/log/btmp, ss shows process info)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.| `--sudoers` | Sudoers file permissions (must be 440), files present, NOPASSWD entries, full sudo access grants |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.local sudo_files=$(find /etc/sudoers /etc/sudoers.d -type f 2>/dev/null | sort)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- **Sudoers**: Avoid NOPASSWD where possible; keep permissions at 440; audit who has full sudo accessFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.if [ -f /etc/sudoers ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- **Sudoers**: Avoid NOPASSWD where possible; keep permissions at 440; audit who has full sudo accessFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.fail "/etc/sudoers permissions are $sudoers_perm (should be 440)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.| `--sudoers` | Sudoers file permissions (must be 440), files present, NOPASSWD entries, full sudo access grants |Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
21 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim laolaoqi: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.