registry / AI-agent control-surface risk / qissa
qissa
Capture condensed decision records from AI-assisted sessions
This report shows the evidence for qissa@0.2.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.3.0, is flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe automatic, overwrite-capable postinstall mutation of third-party AI-agent control surfaces is a concrete blocked control-hijack behavior. No separate exfiltration or network payload was found.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install -g qissa
Impact
Can alter Claude Code and OpenCode agent instructions and commands.
Mechanism
postinstall copies bundled prompts into home agent configuration paths
Policy narrative
On global installation, postinstall invokes applyIntegrations, which creates and overwrites Claude Code and OpenCode prompt/control files in the user's home directory. This changes foreign agent behavior without an explicit setup command.
AI rationale
The automatic, overwrite-capable postinstall mutation of third-party AI-agent control surfaces is a concrete blocked control-hijack behavior. No separate exfiltration or network payload was found.
Evidence
package.jsondist/postinstall.jsdist/chunk-OMVBXF5F.jsintegrations/claude-code/SKILL.mdintegrations/opencode/dlog.md~/.claude/skills/dlog/SKILL.md~/.config/opencode/commands/dlog.md
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 98.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs postinstall.
- dist/postinstall.js activates on global npm install.
- dist/chunk-OMVBXF5F.js writes into Claude Code and OpenCode home control paths.
- Integration writer overwrites existing agent instruction files.
Evidence against
- No network, subprocess, credential harvesting, or remote payload behavior found.
- Bundled integration files are prompt-only and document the dlog CLI behavior.
Behavioral surface
EnvironmentVarsFilesystem
Source & flagged code
3 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node dist/postinstall.js || true
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node dist/postinstall.js || true
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/chunk-OMVBXF5F.jsView file
1// src/lib/agent-integrations.ts
L2: import { existsSync, mkdirSync, copyFileSync } from "fs";
L3: import { dirname, join } from "path";
...
L9: sourceRelativePath: "integrations/claude-code/SKILL.md",
L10: targetRelativePath: join(".claude", "skills", "dlog", "SKILL.md")
L11: },
...
L32: const alreadyExisted = existsSync(targetPath);
L33: mkdirSync(dirname(targetPath), { recursive: true });
L34: copyFileSync(sourcePath, targetPath);
L35: return {
Critical
Ai Agent Control Hijack
Findings
1 Critical1 High3 Medium2 Low
CriticalAi Agent Control Hijackdist/chunk-OMVBXF5F.js
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to qissa@0.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing qissa@0.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.