Skills/npm/rarcane

rarcane@0.4.4

CAUTION

Publisher claims: "Arcane Docker and Compose management over MCP and CLI with authenticated stdio and HTTP." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher dinglebear · joined 8 days agoInstalls 0Last detonated 7d ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-10-27 and scored it 72/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: Authorization escalation language; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 7 s · 2 scenarios · 0 deviations
t+CategoryObserved action
3.3sprocessexec /app/apps/web/node_modules/.bin/tar
3.3sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/tar
3.3sprocessexec /app/node_modules/.bin/tar
3.3sprocessexec /pnpm/tar
3.3sprocessexec /usr/local/sbin/tar
3.3sprocessexec /usr/local/bin/tar
3.3sprocessexec /usr/sbin/tar
3.3sprocessexec /usr/bin/tar
3.3sprocessexec /app/apps/web/node_modules/.bin/gzip
3.3sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/gzip
3.3sprocessexec /app/node_modules/.bin/gzip
3.3sprocessexec /pnpm/gzip
3.3sprocessexec /usr/local/sbin/gzip
3.3sprocessexec /usr/local/bin/gzip
3.3sprocessexec /usr/sbin/gzip
3.3sprocessexec /usr/bin/gzip
7.4sprocessexec /usr/bin/timeout
7.4sprocessexec /app/apps/web/node_modules/.bin/tar
7.4sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/tar
7.4sprocessexec /app/node_modules/.bin/tar
7.4sprocessexec /pnpm/tar
7.4sprocessexec /usr/local/sbin/tar
7.4sprocessexec /usr/local/bin/tar
7.4sprocessexec /usr/sbin/tar
7.4sprocessexec /usr/bin/tar
7.4sprocessexec /app/apps/web/node_modules/.bin/gzip
7.4sprocessexec /root/.cache/node/corepack/v1/pnpm/10.28.0/dist/node-gyp-bin/gzip
7.4sprocessexec /app/node_modules/.bin/gzip
7.4sprocessexec /pnpm/gzip
7.4sprocessexec /usr/local/sbin/gzip
7.4sprocessexec /usr/local/bin/gzip
7.4sprocessexec /usr/sbin/gzip
7.4sprocessexec /usr/bin/gzip
7.4sprocessexec /tmp/ks-detonate-rNXocn/task/home/work/acme-api/.claude/skills/rarcane/vendor/rarcane
7.4sprocessexited 1: /tmp/ks-detonate-rNXocn/task/home/work/acme-api/.claude/skills/rarcane/vendor/rarcane: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/ks-detonate-rNXocn/ta
7.4sclaimedno tools/list reply (exit 1)
7.4sprocessscript backend runs setup only

Static findings

HIGH
Authorization escalation languageREADME.md:328 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathsscripts/check-package.js:285 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

What would make this Verified

8 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Text that tells the agent to ignore its instructions≈ +9 on the totalDelete phrases like "ignore previous instructions", "override", "bypass" from SKILL.md and tool descriptions. Describe what the skill does; do not instruct the agent about other rules.
  2. Unclaimed publisher≈ +8 on the totalClaim dinglebear: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
  4. 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.
  5. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim dinglebear