Is ai-agent-session-center safe to install?

ai-agent-session-center was flagged as CRITICAL RISK (risk score 2145) with 129 findings detected across 82 files. Review the findings before installing.

What security issues were found in ai-agent-session-center?

Sigil detected 129 findings in ai-agent-session-center, including patterns related to install_hooks, code_patterns, obfuscation. See the full scan report for details.

ai-agent-session-center Security Scan — CRITICAL RISK | Sigil

CRITICAL RISK(2145)

v2.9.4

20 March 2026, 09:55 UTC

by Sigil Bot

Risk Score

2145

Findings

129

Files Scanned

82

Provenance

Registry

https://www.npmjs.com/package/ai-agent-session-center/v/2.9.4

Scanned From

https://registry.npmjs.org/ai-agent-session-center/-/ai-agent-session-center-2.9.4.tgz

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

CRITICAL

setup.py executes code at install time

package/dist/client/assets/CyberdromeScene-D3HcbWvm.js:3921

`+re+`
`+B)}else ee!==""?Vt("WebGLProgram: Program Info Log:",ee):(Z===""||ne==="")&&(fe=!1);fe&&(V.diagnostics={runnable:ve,programLog:ee,vertexShader:{log:Z,prefix:b},fragmentShader:{log:ne,prefix:_}})}a.deleteShader(w),a.deleteShader(L),G=new yl(a,P),T=vA(a,P)}let G;this.getUniforms=function(){return G===void 0&&F(this),G};let T;this.getAttributes=function(){return T===void 0&&F(this),T};let y=s.rendererExtensionParallelShaderCompile===!1;return this.isReady=function(){return y===!1&&(y=a.get

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

CRITICAL

setup.py executes code at install time

package/dist/client/assets/CyberdromeScene-D3HcbWvm.js:3972


}`;class nC{constructor(){this.texture=null,this.mesh=null,this.depthNear=0,this.depthFar=0}init(r,s){if(this.texture===null){const l=new Kf(r.texture);(r.depthNear!==s.depthNear||r.depthFar!==s.depthFar)&&(this.depthNear=r.depthNear,this.depthFar=r.depthFar),this.texture=l}}getMesh(r){if(this.texture!==null&&this.mesh===null){const s=r.cameras[0].viewport,l=new ui({vertexShader:eC,fragmentShader:tC,uniforms:{depthColor:{value:this.texture},depthWidth:{value:s.z},depthHeight:{value:s.w}}});this

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

CRITICAL

setup.py executes code at install time

package/dist/client/assets/index-BVmeFvDN.js:53

Set the \`cycles\` parameter to \`"ref"\` to resolve cyclical schemas with defs.`)}for(const a of t.seen.entries()){const o=a[1];if(e===a[0]){s(a);continue}if(t.external){const u=t.external.registry.get(a[0])?.id;if(e!==a[0]&&u){s(a);continue}}if(t.metadataRegistry.get(a[0])?.id){s(a);continue}if(o.cycle){s(a);continue}if(o.count>1&&t.reused==="ref"){s(a);continue}}}function eO(t,e){const n=t.seen.get(e);if(!n)throw new Error("Unprocessed schema. This is a bug in Zod.");const r=a=>{const o=t.see

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

CRITICAL

setup.py executes code at install time

package/dist/client/assets/index-BVmeFvDN.js:181

`&&(this._liveRegionLineCount++,this._liveRegionLineCount===21&&(this._liveRegion.textContent+=d.tooMuchOutput)))}_clearLiveRegion(){this._liveRegion.textContent="",this._liveRegionLineCount=0}_handleKey(S){this._clearLiveRegion(),new RegExp("\\p{Control}","u").test(S)||this._charsToConsume.push(S)}_refreshRows(S,x){this._liveRegionDebouncer.refresh(S,x,this._terminal.rows)}_renderRows(S,x){const E=this._terminal.buffer,A=E.lines.length.toString();for(let T=S;T<=x;T++){const R=E.lines.get(E.ydis

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

CRITICAL

npm lifecycle script — runs automatically on install

package/package.json:21

    "uninstall-hooks": "node hooks/install-hooks.js --uninstall",
    "postinstall": "node bin/postinstall.js && (electron-rebuild -f -w better-sqlite3,node-pty || true)",
    "typecheck": "tsc --noEmit",

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

[![Sigil Scan](https://sigilsec.ai/badge/npm/ai-agent-session-center)](https://sigilsec.ai/scans/D9437E06-3841-4BC6-A4C5-E278D5BF2E37)

HTML

<a href="https://sigilsec.ai/scans/D9437E06-3841-4BC6-A4C5-E278D5BF2E37"><img src="https://sigilsec.ai/badge/npm/ai-agent-session-center" alt="Sigil Scan"></a>