registry / Remote code execution / kempo / 4.4.0

kempo@4.4.0

A fullstack CMS framework for creating websites with user authentication

AI Security Review

scanned 2d ago · by lpm-firewall-ai

The CLI contains a real command-injection vulnerability when its project or database name contains shell syntax. Because it requires invoking setup with such a name and does not establish publisher-directed attack behavior, warn rather than block.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user invokes kempo init, setup creates a new container, and the project directory name or entered database name contains shell syntax.

Impact

A crafted name can cause additional local shell commands to run during setup.

Mechanism

The CLI interpolates the name into docker stop and docker rm commands executed through execSync.

AI rationale

Evidence

bin/cli.js

Decision evidence

public snapshot

AI called this Suspicious at 88.0% confidence as Critical Vulnerability with medium false-positive risk.

Evidence for warning

The CLI accepts only the init command and sets defaults from a project name derived from the current directory.
In interactive setup, the entered database name becomes the container name; with defaults, the project directory name is used.
The new-container path interpolates that name into shell commands, creating a conditional command-injection vulnerability.

Evidence against

The risky commands are reached through the user-invoked init setup path and only when creating a new container.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStringsMinifiedUrlStrings

ManifestNo manifest risk signals triggered.

scanned 308 file(s), 823 KB of source, external domains: docs.docker.com, lexical.dev, raw.githubusercontent.com, resend.com

Source & flagged code

6 flagged

bin/cli.jsView file

Lines 1-25javascript

1#!/usr/bin/env node

3import { existsSync, cpSync, mkdirSync, writeFileSync, rmSync } from 'fs';

4import { fileURLToPath, pathToFileURL } from 'url';

5import { join, dirname, basename } from 'path';

6import { execSync, spawnSync } from 'child_process';

7import crypto from 'crypto';

High

Child Process

Package source references child process execution.

bin/cli.jsView on unpkg · L5

8import inquirer from 'inquirer';

10const args = process.argv.slice(2);

11const command = args[0];

12const useDefaults = args.includes('-y') || args.includes('--yes');

14if(command !== 'init'){

15 console.log('Usage: npx kempo init [-y|--yes]');

16 process.exit(1);

17}

19const __filename = fileURLToPath(import.meta.url);

20const __dirname = dirname(__filename);

21const moduleRoot = join(__dirname, '..');

22const projectDir = process.cwd();

23const projectName = basename(projectDir);

25/*

High

Entrypoint Build Divergence

Manifest entrypoint contains risky behavior absent from dist/build output.

bin/cli.jsView on unpkg · L5

Lines 377-444javascript

377

378writeFileSync(join(projectDir, '.env'),

379`# Database

380DATABASE_URL=${databaseUrl}

381

382# Email${emailServiceSkipped ? '\n# Configure your email service — update the values below' : ''}

383RESEND_API_KEY=${

•matchType = previous_version_dangerous_delta matchedPackage = kempo@4.2.22 matchedIdentity = npm:a2VtcG8:4.2.22 similarity = 0.683 summary = stored previous version shares package body but lacks this dangerous source file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

bin/cli.jsView on unpkg

middleware/kempo.jsView file

Lines 82-122javascript

82 return { filePath: join(base, head), params: {} };

83 }

84 }

85 if(rest.length === 0){

86 for(const entry

Source & flagged code

6 flagged · loading source

bin/cli.jsView file

Critical

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

bin/cli.jsView on unpkg

5import { join, dirname, basename } from 'path'; L6: import { execSync, spawnSync } from 'child_process'; L7: import crypto from 'crypto';

High

Child Process

Package source references child process execution.

bin/cli.jsView on unpkg · L5

424stdio: 'inherit', L425: shell: true L426: });

High

Shell

Package source references shell execution.

bin/cli.jsView on unpkg · L424

5Manifest entrypoint (manifest.bin) carries capability families absent from dist/build output: environment+network, execution+network L5: import { join, dirname, basename } from 'path'; L6: import { execSync, spawnSync } from 'child_process'; L7: import crypto from 'crypto'; ... L19: const __filename = fileURLToPath(import.meta.url); L20: const __dirname = dirname(__filename); L21: const moduleRoot = join(__dirname, '..'); ... L25: /* L26: package.json L27: */ ... L65: const waitForPostgres = async (containerName, dbName = 'postgres') => { L66: process.stdout.write('Waiting for Postgres to be ready'); L67: for(let i = 0; i < 30; i++){

Findings

1 Critical4 High4 Medium4 Low

CriticalPrevious Version Dangerous Deltabin/cli.js

HighChild Processbin/cli.js

HighShellbin/cli.js

HighEntrypoint Build Divergencebin/cli.js

HighRuntime Package Installbin/cli.js

MediumDynamic Requiremiddleware/kempo.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to kempo@4.4.0.

See all versions of kempo for other recorded verdicts.

Review the evidence and your use of kempo@4.4.0 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-21 04:04:33.625Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.