Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Authorized security-assessment profile for DeepSeek Harness with scoped network tools, container-backed shell, authorization guard, and durable evidence.
- Scoped network tools
- Container-backed shell
- Durable evidence collection
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add github:cyzlmh/dsh-cyber-secInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.1
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
current (registry 2026-11-12) · 8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-11 · 8 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
09-24 → 11-11 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
Verification & Compatibility○ Ecosystem plugin
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| f59e1d | · | · | · | · | · |
| d909c7 | · | · | · | · | · |
| 81ef17 | ○ | ○ | ○ | ○ | ✗ |
f59e1dgithub○ 1 ecosystem plugin2026-09-04
github:cyzlmh/dsh-cyber-sec
○dsh 0.1.2-rc.12026-09-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:cyzlmh/dsh-cyber-sec#f59e1d
ID: dsh-cyber-sec@f59e1d@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
d909c7github2026-08-28
https://github.com/cyzlmh/dsh-cyber-sec
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
81ef17github○ 16 ecosystem plugin2 failed2026-11-06
https://github.com/cyzlmh/dsh-cyber-sec
○dsh 0.2.2-rc.12026-11-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-rc.52026-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-rc.32026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-rc.22026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.42026-10-16Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.22026-10-08Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.0-rc.12026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.22026-09-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.12026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.6-alpha.22026-09-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-19 · expires: 2026-09-26
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.3-alpha.22026-09-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.2-alpha.12026-09-02Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-cyber-sec@81ef17@dsh0.1.2-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-02 · expires: 2026-12-01
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/cyzlmh/dsh-cyber-sec (version unstated)
ID: dsh-cyber-sec@81ef17@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-cyber-sec@d909c7…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-cyber-sec/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low; dynamic medium (authoritative when present) → overall medium.
v0.0.10.0.1git2026-11-130.0.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (11)
- criticaldestructiveRm · destructive
docker/stage2.sh:65rm -rf /var/lib/apt/lists/* /tmp/go /root/.cargo /root/.rustup - criticaldestructiveRm · destructive
docker/stage3.sh:73rm -rf /var/lib/apt/lists/* /root/.cargo /root/.rustup /tmp/terrascan.tar.gz - criticaldestructiveRm · destructive
docker/stage4.sh:33rm -rf /tmp/HashPump - criticaldestructiveRm · destructive
docker/stage4.sh:62rm -rf /var/lib/apt/lists/* /root/.cargo /root/.rustup - criticaldestructiveRm · destructive
docker/stage5.sh:51rm -rf /var/lib/apt/lists/* /root/.cargo /root/.rustup /tmp/gm-req.txt - criticaldestructiveRm · destructive
docker/stage6.sh:23rm -rf /var/lib/apt/lists/* - criticaldestructiveRm · destructive
probe/tools-seam-probe.ts:25assert.throws(() => validateScanTarget('app.example.test; rm -rf /'), /IPv4 address or domain/) - warningcurlDownload · network
docker/stage2.sh:53curl -fsSL -o /usr/local/bin/linpeas.sh \ - warningcurlDownload · network
docker/stage3.sh:35curl -fsSL "$asset_url" -o /tmp/terrascan.tar.gz \ - warningcurlDownload · network
docker/stage6.sh:17curl -fsSL -m 120 -o /usr/local/bin/pwninit \ - warningnetIp · network
examples/cybergym/judge.sh:14SERVER=${SERVER:-http://127.0.0.1:8666}
show 3 audit findings
- mediumUnverified release binary downloaded and executed during image build (pwninit)
docker/stage6.sh:18The build stage fetches a prebuilt binary over HTTPS and immediately executes it as root inside the image, with no checksum or signature verification. Whoever controls the upstream GitHub release asset (or the TLS path / release re-upload) gets code execution in the build and ships that binary into an image that later runs against live targets.
- mediumTool script and binary fetched from mutable upstream URLs without integrity check (linpeas, terrascan)
docker/stage2.sh:53linpeas.sh is pulled from the mutable 'latest' release path and marked executable; docker/stage3.sh does the same for the terrascan tarball selected from the GitHub API's latest release. Any upstream compromise or re-tagged release silently lands an attacker-controlled executable in an image whose whole purpose is to run these tools with elevated privileges against targets.
- lowRecursive rm -rf on environment-derived path in example adapter
examples/cybergym/run_task.sh:75A recursively destructive delete runs by default (D7_RESET defaults to 1) on a path taken from $DSH_HOME; if the operator exports DSH_HOME pointing at an unintended directory, that directory's profiles/node_modules is deleted without any sanity check. Blast radius is a rebuildable dependency tree, so impact is limited.
Static fail not reproduced: the only runtime plugin reads local SKILL.md files; real risks are build-time unverified binary downloads (medium) plus a destructive rm -rf in an example script.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-08-25 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 5 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/cyzlmh/dsh-cyber-sec
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is dsh-cyber-sec?
dsh-cyber-sec is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install dsh-cyber-sec?
Run dsh plugin --profile web add github:cyzlmh/dsh-cyber-sec in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-13 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.