netexec-mcp@1.0.10
CAUTION· not startedPublisher claims: "MCP server that drives NetExec (nxc) for authorized security testing." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 68/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; Credential pass-through configuration; Credential pass-through configuration. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
path). Applying it (review first!) typically: `sudo sh -c 'cat <file> >> /etc/hosts'`.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Reports OS/domain and the auth result (`[+]`/`[-]`). Pass credentials to bind,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.the auth result (`[+]`, with `Pwn3d!` when the account can log in). Pass credentialsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"sudo sh -c 'cat {output_file} >> /etc/hosts'"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.(runs sudo and copies ``/etc/shadow`` to verify the user can reach root).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.f"sudo sh -c 'cat {output_file} >> /etc/hosts'"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""Actively verify the user can escalate to root via sudo (`--sudo-check`).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.role). Pass credentials to authenticate, or none to fingerprint the service.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.does a *non-intrusive* privilege check (``id; sudo -ln``), reportingFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.non-intrusive `id; sudo -ln` check). Authenticate with `username`+`password`, or aFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# and the alphabet chose the one that kills. Plural only: "kill a process" stays on taskkill,Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.`/etc/shadow` on the target.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.upload (chmod 777) and ``chmod`` of remote files.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.(runs sudo and copies ``/etc/shadow`` to verify the user can reach root).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.open a remote shell). Pass credentials to authenticate, or none to probe whetherFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Unlike the passive check in `ssh_enum_hosts`, this *runs* sudo and copiesFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.2. The kill therefore targets the group, not the process.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.`/etc/shadow` to a temp file to confirm root access. `method` is "sudo-stdin"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.share (written with chmod 777). `share` selects the export. OFFENSIVE-GATEDFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."""Change permissions of a remote NFS file (`--chmod <perms> <file>`).Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.except Exception as exc: # noqa: BLE001 -- never let a dispatch failure kill the turnFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.account is a local admin). Pass credentials to authenticate, or none to fingerprintFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# and "kill" points there so "kill processes" does too.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.would kill them at the instant of expiry and every byte still in the pipe would beFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for netexec-mcp@1.0.10 as of 32 h ago. This is the package itself, not its dependencies.
What would make this Verified
12 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim mpgn: 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.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- 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.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.