Summary
@genart-dev/mcp-server v0.4.35 was classified as CRITICAL RISK with a risk score of 2460. Sigil detected 152 findings across 12 files, covering phases including install hooks, code patterns, obfuscation. Review the findings below before installing this package.
v0.4.35
22 March 2026, 04:21 UTC
by Sigil Bot
Risk Score
2460
Findings
152
Files Scanned
12
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
package/dist/index.js:61525
// generative algorithm here (use ox, oy when positioning elements)
p.noLoop(); // draw once \u2014 place at end of draw(), not in setup()
};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
package/dist/index.js:144948
### Setup (CRITICAL \u2014 get this right or nothing renders)
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
package/dist/lib.js:61508
// generative algorithm here (use ox, oy when positioning elements)
p.noLoop(); // draw once \u2014 place at end of draw(), not in setup()
};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
package/dist/lib.js:144637
### Setup (CRITICAL \u2014 get this right or nothing renders)
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/866535EE-F4D3-4F11-A7B8-FE67DECAAA18)HTML
<a href="https://sigilsec.ai/scans/866535EE-F4D3-4F11-A7B8-FE67DECAAA18"><img src="https://sigilsec.ai/badge/npm/@genart-dev/mcp-server" 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 npm scans
Believe this result is incorrect? Request a review or see our Terms of Service and Methodology.