registry / @tokensrc/codex / 1.14.28

@tokensrc/codex@1.14.28

Standalone Codex account selection, authentication and launcher module.

AI Security Review

scanned 28d ago · by lpm-firewall-ai

The package can install persistent shortcut launchers that automatically retrieve and execute a newer registry release. This turns later shortcut launches into remote code execution through the package registry.

Static reason

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

Trigger

A user runs the shortcut install command and later starts one of the installed launchers.

Impact

A future published release can run with the launching user's permissions.

Mechanism

Persistent launcher auto-update and execution of registry-downloaded JavaScript.

Attack narrative

The user-facing shortcut installer copies a bootstrap program into a persistent command directory. On each later shortcut launch, that program asks the registry for the latest version of @tokensrc/codex, installs it into a local cache, selects its bin entrypoint, and runs it. Because the downloaded JavaScript is executed automatically without a pinned artifact or signature, a later registry release controls the user's launcher.

AI rationale

This is a concrete persistent remote payload mechanism: a locally installed launcher automatically downloads and executes later package code. It is not an npm install lifecycle hook, but it creates an equivalent user-level execution path.

Evidence

assets/shortcut-bootstrap.cjsdist/shortcuts.jsdist/config.jsdist/commands.js

Network endpoints1

registry.npmjs.org/

@tokensrc/codex@1.14.28

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code