Summary
vinkius-labs/vurb.ts v2026-03-19 was classified as CRITICAL RISK with a risk score of 3658. Sigil detected 326 findings across 772 files, covering phases including provenance, install hooks, code patterns, network exfiltration, obfuscation, credential access. Review the findings below before installing this package.
Package description: Vurb.ts - The TypeScript Framework for MCP Servers. Type-safe tools, structured AI perception, and built-in security. Deploy once — every AI assistant connects instantly.
v2026-03-19
20 March 2026, 00:41 UTC
by Sigil Bot
Risk Score
3658
Findings
326
Files Scanned
772
Provenance
Findings by Phase
Phase Ordering
Phases are ordered by criticality, with the most dangerous at the top. Click any phase header to expand or collapse its findings. Critical phases are expanded by default.
install-pip-setup-exec
CRITICALsetup.py executes code at install time
repo/CHANGELOG.md:559
- **`DevServer.performReload` collects builders in disposable registry (Bug #42)** — `performReload` created a local `reloadRegistry`, called `setup(reloadRegistry)`, collected builders, but never transferred them to the real MCP server's registry. The client received `notifications/tools/list_changed` but the actual tool list hadn't changed — hot-reload was effectively a no-op. Fixed by accepting an optional `registry` in `DevServerConfig` and transferring collected builders after each reload Why was this flagged?
This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.
install-pip-setup-exec
CRITICALsetup.py executes code at install time
repo/docs/enterprise/.vitepress/cache/deps/chunk-TBFXGU3P.js:1651
const define = defineComponent({
setup(_, { slots }) {
return () => {Why was this flagged?
This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.
install-pip-setup-exec
CRITICALsetup.py executes code at install time
repo/packages/core/tests/cli/deployEdgeStub-bug151.test.ts:156
name: 'vurb-edge-stub',
setup(build) {
build.onResolve({ filter: builtinFilter }, (args) => ({Why was this flagged?
This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.
Badge
Markdown
[](https://sigilsec.ai/scans/4F44181C-FCA7-4BB4-88C4-ED19E6644076)HTML
<a href="https://sigilsec.ai/scans/4F44181C-FCA7-4BB4-88C4-ED19E6644076"><img src="https://sigilsec.ai/badge/github/vinkius-labs/vurb.ts" alt="Sigil Scan"></a>Run This Scan Yourself
Scan your own packages
Run Sigil locally to audit any package before it touches your codebase.
Early Access
Get cloud scanning, threat intel, and CI/CD integration.
Join 150+ developers on the waitlist.
Get threat intelligence and product updates
Security research, new threat signatures, and product updates. No spam.
Other github scans
Believe this result is incorrect? Request a review or see our Terms of Service and Methodology.