registry / Malware / lightbase-edge / 0.1.15

lightbase-edge@0.1.15

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 2d ago · by lpm-firewall-ai

The CLI is also the package’s main module, and its top-level dispatch defaults to deploy. In a configured project, importing it can therefore use the user’s deploy token to update a remote manifest without an explicit deploy request, which meets the automatic key-use rule.

Static reason

One or more suspicious static signals were detected.

Trigger

Import cli.mjs from a project directory with Lightbase configuration, build inputs, and credentials; the CLI defaults to deploy when no command argument is present.

Impact

An import can publish or update the configured app manifest using the user’s deploy token.

Mechanism

Top-level command dispatch invokes cmdDeploy, which bundles the app and sends the deploy token in a manifest PUT to the configured Lightbase URL.

Attack narrative

When imported in a suitably configured project, the package’s main module defaults to the deploy command and invokes it at top level. If the project has the expected build inputs and Lightbase credentials, this bundles the app and sends its deploy token in a manifest registration request, potentially updating the remote app without an explicit deploy request.

AI rationale

Evidence

package.jsoncli.mjsdist/_lb-manifest.jsondist/_lb/{appId}/server.js

Network endpoints1

${LIGHTBASE_URL|LIGHTBASE_BASE_URL}/api/v1/projects/{projectId}/edge/apps/{appId}/manifest

Decision evidence

public snapshot

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

Evidence for block

The package exposes cli.mjs as both its executable and its main module.
The CLI defaults to deploy and dispatches the selected command at top level, so importing the main module can start a deployment.
Deploy reads a Lightbase URL, project ID, and deploy token from environment variables.
Deployment sends the token in an authenticated PUT that registers an app manifest.

Evidence against

The package has no lifecycle scripts of its own.
The manifest request goes to the configured Lightbase service, consistent with the package’s deployment purpose.
The inspected esbuild postinstall code handles platform-specific binary setup.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 106 KB of source

Source & flagged code

7 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

2039const cmd = process.argv[2] || 'deploy'; // BismiLLAH (0.1.6 — always-produce CI): `deploy`/`optimize` NEVER exit earl

High

Ai Review Evidence

The CLI defaults to deploy and dispatches the selected command at top level, so importing the main module can start a deployment.

cli.mjsView on unpkg · L2039

2061deploy: () => cmdDeploy({ tolerant: !enforcedCfg }), // BismiLLAH (0.1.2): `optimize` is the pos

High

Ai Review Evidence

The CLI defaults to deploy and dispatches the selected command at top level, so importing the main module can start a deployment.

cli.mjsView on unpkg · L2061

Findings

7 High3 Medium2 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

Affected versions and remediation

This report applies to lightbase-edge@0.1.15.

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

Avoid installing lightbase-edge@0.1.15. 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-03 10:53:27.548Z (UTC).

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

registry / Malware / lightbase-edge / 0.1.15

lightbase-edge@0.1.15

AI Security Review

scanned 2d ago · by lpm-firewall-ai

Static reason

One or more suspicious static signals were detected.

Trigger

Import cli.mjs from a project directory with Lightbase configuration, build inputs, and credentials; the CLI defaults to deploy when no command argument is present.

Impact

An import can publish or update the configured app manifest using the user’s deploy token.

Mechanism

Top-level command dispatch invokes cmdDeploy, which bundles the app and sends the deploy token in a manifest PUT to the configured Lightbase URL.

Attack narrative

AI rationale

Evidence

package.jsoncli.mjsdist/_lb-manifest.jsondist/_lb/{appId}/server.js

Network endpoints1

${LIGHTBASE_URL|LIGHTBASE_BASE_URL}/api/v1/projects/{projectId}/edge/apps/{appId}/manifest

Decision evidence

public snapshot

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

Evidence for block

The package exposes cli.mjs as both its executable and its main module.
The CLI defaults to deploy and dispatches the selected command at top level, so importing the main module can start a deployment.
Deploy reads a Lightbase URL, project ID, and deploy token from environment variables.
Deployment sends the token in an authenticated PUT that registers an app manifest.

Evidence against

The package has no lifecycle scripts of its own.
The manifest request goes to the configured Lightbase service, consistent with the package’s deployment purpose.
The inspected esbuild postinstall code handles platform-specific binary setup.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 106 KB of source

Source & flagged code

7 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

2039const cmd = process.argv[2] || 'deploy'; // BismiLLAH (0.1.6 — always-produce CI): `deploy`/`optimize` NEVER exit earl

High

Ai Review Evidence

The CLI defaults to deploy and dispatches the selected command at top level, so importing the main module can start a deployment.

cli.mjsView on unpkg · L2039

2061deploy: () => cmdDeploy({ tolerant: !enforcedCfg }), // BismiLLAH (0.1.2): `optimize` is the pos

High

Ai Review Evidence

The CLI defaults to deploy and dispatches the selected command at top level, so importing the main module can start a deployment.

cli.mjsView on unpkg · L2061

Findings

7 High3 Medium2 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

Affected versions and remediation

This report applies to lightbase-edge@0.1.15.

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

Avoid installing lightbase-edge@0.1.15. 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-03 10:53:27.548Z (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