Summary
agentic-qe v3.8.5 was classified as CRITICAL RISK with a risk score of 15323. Sigil detected 1287 findings across 3655 files, covering phases including network exfiltration, code patterns, credential access, obfuscation, install hooks. Review the findings below before installing this package.
v3.8.5
22 March 2026, 09:45 UTC
by Sigil Bot
Risk Score
15323
Findings
1287
Files Scanned
3655
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/cli/bundle.js:1683
describe('{{consumerName}} -> {{providerName}} contract', () => {
beforeAll(() => pact.setup());
afterAll(() => pact.finalize());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/cli/bundle.js:2431
`,i+=` @BeforeEach
`,i+=` void setUp() {
`,i+=` subject = new ${e.name}();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/cli/bundle.js:3692
`)}buildSyntheticHistory(e){let u=Math.max(e.usageCount,1),t=Math.round(u*e.successRate),a=[];for(let n=0;n<t;n++)a.push({success:!0});for(let n=0;n<u-t;n++)a.push({success:!1});return a}inferTag(e){let u=e.name.toLowerCase();return u.includes("null")||u.includes("undefined")?"null-check":u.includes("empty")||u.includes("boundary")||u.includes("zero")?"boundary":u.includes("async")||u.includes("promise")||u.includes("reject")?"async-error":u.includes("error")||u.includes("throw")||u.includes("exWhy 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/mcp/bundle.js:1310
`,r+=` @BeforeEach
`,r+=` void setUp() {
`,r+=` subject = new ${e.name}();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/mcp/bundle.js:2592
`);for(let a of t){let n=a.match(/^\s*import\s+'([^']+)'/);n&&u.push({module:n[1],namedImports:[],isTypeOnly:!1})}return u}parseParams(e){if(!e.trim())return[];let u=e.replace(/[{}[\]]/g,"");return En(u).map(t=>t.trim()).filter(t=>t).map(t=>{let a=t.replace("required ","").trim().split(/\s+/),n=a[a.length-1]||"",r=a.slice(0,-1).join(" ")||void 0;return{name:n,type:r,isOptional:t.includes("?")||t.includes("{"),defaultValue:void 0}})}},NC=class{parsers=new Map;constructor(){this.register(new SC),tWhy 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/mcp/bundle.js:5116
describe('{{consumerName}} -> {{providerName}} contract', () => {
beforeAll(() => pact.setup());
afterAll(() => pact.finalize());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-npm-postinstall
CRITICALnpm lifecycle script — runs automatically on install
package/package.json:44
"scripts": {
"preinstall": "node scripts/preinstall.cjs || true",
"postinstall": "node scripts/postinstall.cjs",Why was this flagged?
npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.
install-npm-postinstall
CRITICALnpm lifecycle script — runs automatically on install
package/package.json:45
"preinstall": "node scripts/preinstall.cjs || true",
"postinstall": "node scripts/postinstall.cjs",
"build": "tsc && npm run build:cli && npm run build:mcp",Why was this flagged?
npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.
Badge
Markdown
[](https://sigilsec.ai/scans/4A5D6C14-4800-4512-BE18-28F3ECDCE3F1)HTML
<a href="https://sigilsec.ai/scans/4A5D6C14-4800-4512-BE18-28F3ECDCE3F1"><img src="https://sigilsec.ai/badge/npm/agentic-qe" 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.