@volter/supercode@0.5.250: Suspicious npm security report (Warn) | LPM Firewall

Loading npm security reports…

@volter/supercode@0.5.250: Suspicious npm security report (Warn) | LPM Firewall

Source & flagged code

6 flagged · loading source

package.jsonView file

•scripts.postinstall = node lib/release.mjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

13"scripts": { "postinstall": "node lib/release.mjs" }, "dependencies"

Medium

Ai Review Evidence

The package runs lib/release.mjs automatically after installation.

package.jsonView on unpkg · L13

bin/supercode.jsView file

7L8: const { spawnSync } = require("child_process"); L9: const { pathToFileURL } = require("url");

Medium

Dynamic Require

Package source references dynamic require/import behavior.

bin/supercode.jsView on unpkg · L7

lib/skills.mjsView file

8Install-time code directly mutates a foreign AI-agent control surface: L12: // `supercode teams connect` (sdk/teams bin/workspace.mjs). L13: import { cpSync, existsSync, lstatSync, mkdirSync, readFileSync, readdirSync, readlinkSync, renameSync, rmSync, statSync, writeFileSync } from 'node:fs'; L14: import { createHash } from 'node:crypto'; ... L25: const HARNESS_HOMES = [ L26: { harness: 'claude', home: () => process.env.CLAUDE_CONFIG_DIR || join(homedir(), '.claude') }, L27: { harness: 'codex', home: () => process.env.CODEX_HOME || join(homedir(), '.codex') }, L28: ]; ... L73: try { L74: mkdirSync(folder, { recursive: true }); L75: // written beside it and moved into place, so a harness reading skills never sees half of one ... L77: rmSync(staged, { recursive: true, force: true }); L78: c

Critical

Ai Agent Control Hijack

Source creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.

lib/skills.mjsView on unpkg · L8

49/** Put the release's skills into every harness home here; answers a line per skill and home. */ export function installSkills({ version = release() } = {}) { const source = join(PACKAGE, 'skills'); if (!existsSync(source)) return ['this release carries no skills']; const skills = readdirSync(source, { withFileTypes: true }).filter((entry) => entry.isDirectory() && existsSync(join(source, entry.name, 'SKILL.md'

Medium

Ai Review Evidence

The release hook installs this release's bundled skills into existing Claude and Codex harness homes when the machine's own package install runs.

lib/skills.mjsView on unpkg · L49

60const target = join(folder, name); let stat = null; try { stat = lstatSync(target); } catch { /* absent */ } if (stat?.isSymbolicLink()) { report.push(`${harness} ${name}: kept, a link someone made (${readlinkSync(target)})`); continue; } if (stat && !existsSync(join(target, MARKER))) { report.push(`${harness} ${name}: kept, a folder supercode did not write`); continue; } const shipped = dig

Source & flagged code

6 flagged

package.jsonView file

Lines 1-27json

1{

2 "name": "@volter/supercode",

3 "version": "0.5.250",

4 "description": "Volter Harness: a lightweight, customizable AI coding agent CLI — any model via OpenRouter; natively continues Claude Code and Codex sessions.",

5 "repository": { "type": "git", "url": "git+https://github.com/volter-ai/supercode.git" },

6 "homepage": "https://github.com/volter-ai/supercode#readme",

7 "bugs": { "url": "https://github.com/volter-ai/supercode/issues" },

8 "license": "MIT OR Apache-2.0",

9 "keywords": ["ai", "agent", "llm", "coding", "cli", "openrouter", "claude", "codex"],

10 "bin": { "supercode": "bin/supercode.js" },

11 "files": ["bin/", "lib/", "skills/"],

12 "engines": { "node": ">=16" },

13 "scripts": { "postinstall": "node lib/release.mjs" },

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L13

14 "dependencies": {

Medium

Ai Review Evidence

The package runs lib/release.mjs automatically after installation.

package.jsonView on unpkg · L13

15 "@volter/supercode-orchestrator": "0.5.93",

16 "@volter/supercode-harness-sdk": "0.3.78",

17 "@volter/supercode-teams": "0.3.136"

18 },

19 "optionalDependencies": {

20 "@volter/supercode-cli-darwin-arm64": "0.5.250",

21 "@volter/supercode-cli-darwin-x64": "0.5.250",

22 "@volter/supercode-cli-linux-x64": "0.5.250",

23 "@volter/supercode-cli-linux-arm64": "0.5.250",

24 "@volter/supercode-cli-win32-x64": "0.5.250"

25 }

26}

27

bin/supercode.jsView file

Lines 1-27javascript

1#!/usr/bin/env node

2// The `supercode` front door. A command that has moved to TypeScript (lib/commands.mjs) is served here, in Node; every

3// other command goes to the native binary, which ships in a platform-specific optional dependency

4// (`@volter/supercode-cli-<os>-<cpu>`, npm installs only the one matching the host), with argv, stdio (so the

5// interactive REPL/TTY works) and the exit code forwarded as before (arc t_08d00e09, route step 2).

6"use strict";

7

8const { spawnSync } = require

lib/skills.mjsView file

Lines 1-80javascript

1// `supercode skills install`: the skills this release carries (skills/<name>/SKILL.md beside lib/), put into every

2// agent harness's skills folder in this OS user's home, and the messaging tools registered with each harness

3// (t_266912ff). A release ships its skills: a machine had them only where someone linked a checkout of agent-skills

4// by hand, so an agent on a machine (or under WSL) with none did not know supercode.

5//

6// Idempotent. A skill folder this installs carries a marker (`.supercode-release`: the release that wrote it and a hash

7// of what it wrote) and is replaced whole when another release's; a folder or link someone else put there is theirs,

8// and so is one edited since supercode wrote it (its files no longer hash to its marker's): both are left alone, said

9// in the report. Only this OS user's home is written (under sudo, root's): a Windows install does not reach a WSL