registry / Malware / lightbase-edge / 0.1.17

lightbase-edge@0.1.17

The Lightbase Edge deploy tool: full-Node SSR for any Node codebase (Astro, Nuxt, Next, custom servers) served through the Lightbase edge gateway with a static CDN front. Zero edge functions, zero provisioning, zero rewrites — bundles your server, publish

AI Security Review

scanned 2h ago · by lpm-firewall-ai

The package's main entry performs a deploy by default when imported, using ambient Lightbase credentials to update an app manifest. Although the destination is the configured service and deployment matches the CLI's purpose, automatic use of the user's token on import meets the stated malicious automatic-action rule.

Static reason

One or more suspicious static signals were detected.

Trigger

Importing cli.mjs without a command argument; the module dispatches immediately and defaults to deploy.

Impact

An import can publish or update the configured app manifest and use the user's deployment token without an explicit deploy command.

Mechanism

The deploy command reads the configured Lightbase token and sends it in an authenticated manifest PUT to the configured service URL.

Attack narrative

The package declares cli.mjs as its main entry, but that file executes its command dispatcher at module top level and defaults to deploy. Importing it can therefore run a deployment using LIGHTBASE_DEPLOY_TOKEN or LIGHTBASE_API_KEY from the environment, sending the token in a manifest PUT to the configured Lightbase service and updating the app without an explicit deploy request.

AI rationale

Evidence

package.jsoncli.mjs${cfg.staticOut}/_lb-manifest.json${cfg.staticOut}/_lb/{appId}/{versionDir}/server.js

Network endpoints1

Configured LIGHTBASE_URL or LIGHTBASE_BASE_URL host: /api/v1/projects/{projectId}/edge/apps/{appId}/manifest

Decision evidence

public snapshot

AI called this Malicious at 92.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json exposes cli.mjs as both the package main and executable.
cli.mjs defaults to the deploy command and invokes the selected command at module top level, so importing the main entry runs deploy.
The deploy command reads LIGHTBASE_DEPLOY_TOKEN or LIGHTBASE_API_KEY from the environment.
Deploy sends a PUT with that token to the configured Lightbase URL to register or update the app manifest.

Evidence against

The package is described as a Lightbase deployment CLI, and deployment is its stated purpose.
The token is sent to the configured Lightbase service URL, not to an unrelated collector.
Deployment requires Lightbase configuration and credentials to make the authenticated request.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 112 KB of source, external domains: www.w3.org

Source & flagged code

6 flagged

cli.mjsView file

146package = lightbase-edge; repositoryIdentity = lightbase; dependency = esbuild L146: // (monorepo symlink — npm installs a REAL symlink, not a copy), ESM L147: // import('esbuild') resolves from the package's REAL path, where the host L148: // project's esbuild is invisible → "esbuild is required" on every deploy.

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

cli.mjsView on unpkg · L146

2114const cmd = process.argv[2] || 'deploy'; // BismiLLAH (0.1.6 — always-produce CI): `deploy`/`optimize` NEVER exit early — // without complete credentials they assemble the Pages output a

High

Ai Review Evidence

cli.mjs defaults to the deploy command and invokes the selected command at module top level, so importing the main entry runs deploy.

cli.mjsView on unpkg · L2114

2148(commands[cmd] ?? die(`Unknown command: ${cmd} (use init|build|deploy|register|optimize|status|logs)`))().catch((e) => die(e && e.message));

High

Ai Review Evidence

cli.mjs defaults to the deploy command and invokes the selected command at module top level, so importing the main entry runs deploy.

Findings

6 High3 Medium3 Low

HighCopied Package Dependency Bridgecli.mjs

HighAi Review Evidencepackage.json

HighAi Review Evidencecli.mjs

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to lightbase-edge@0.1.17.

See all versions of lightbase-edge for other recorded verdicts.

Avoid installing lightbase-edge@0.1.17. 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: 2026-11-04 22:42:06.784Z (UTC).

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

registry / Malware / lightbase-edge / 0.1.17

lightbase-edge@0.1.17

AI Security Review

scanned 2h ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.

Trigger

Importing cli.mjs without a command argument; the module dispatches immediately and defaults to deploy.

Impact

An import can publish or update the configured app manifest and use the user's deployment token without an explicit deploy command.

Mechanism

The deploy command reads the configured Lightbase token and sends it in an authenticated manifest PUT to the configured service URL.

Attack narrative

AI rationale

Evidence

package.jsoncli.mjs${cfg.staticOut}/_lb-manifest.json${cfg.staticOut}/_lb/{appId}/{versionDir}/server.js

Network endpoints1

Configured LIGHTBASE_URL or LIGHTBASE_BASE_URL host: /api/v1/projects/{projectId}/edge/apps/{appId}/manifest

Decision evidence

public snapshot

AI called this Malicious at 92.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json exposes cli.mjs as both the package main and executable.
cli.mjs defaults to the deploy command and invokes the selected command at module top level, so importing the main entry runs deploy.
The deploy command reads LIGHTBASE_DEPLOY_TOKEN or LIGHTBASE_API_KEY from the environment.
Deploy sends a PUT with that token to the configured Lightbase URL to register or update the app manifest.

Evidence against

The package is described as a Lightbase deployment CLI, and deployment is its stated purpose.
The token is sent to the configured Lightbase service URL, not to an unrelated collector.
Deployment requires Lightbase configuration and credentials to make the authenticated request.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 112 KB of source, external domains: www.w3.org

Source & flagged code

6 flagged

cli.mjsView file

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

cli.mjsView on unpkg · L146

2114const cmd = process.argv[2] || 'deploy'; // BismiLLAH (0.1.6 — always-produce CI): `deploy`/`optimize` NEVER exit early — // without complete credentials they assemble the Pages output a

High

Ai Review Evidence

cli.mjs defaults to the deploy command and invokes the selected command at module top level, so importing the main entry runs deploy.

cli.mjsView on unpkg · L2114

2148(commands[cmd] ?? die(`Unknown command: ${cmd} (use init|build|deploy|register|optimize|status|logs)`))().catch((e) => die(e && e.message));

High

Ai Review Evidence

cli.mjs defaults to the deploy command and invokes the selected command at module top level, so importing the main entry runs deploy.

Findings

6 High3 Medium3 Low

HighCopied Package Dependency Bridgecli.mjs

HighAi Review Evidencepackage.json

HighAi Review Evidencecli.mjs

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to lightbase-edge@0.1.17.

See all versions of lightbase-edge for other recorded verdicts.

Avoid installing lightbase-edge@0.1.17. 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: 2026-11-04 22:42:06.784Z (UTC).

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

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Related packages

Other malware packages

Behavioral surface

Related packages

Other malware packages