registry / kepler / 2.6.999

kepler@2.6.999

Generated package

AI Security Review

scanned 10d ago · by lpm-firewall-ai

Installing kepler fetches an opaque dependency from artifacts.yosiroute.com. Its shrinkwrap metadata declares an install script, but that dependency's source is absent from this package.

Static reason

No blocking static signals were detected.

Trigger

npm install kepler

Impact

Uninspected code may execute during dependency installation.

Mechanism

remote install-script dependency carrier

Rationale

No confirmed malicious action exists in kepler's own source, so a block is not justified. The uninspectable remote install-script dependency is a real staged-payload risk and warrants a warning.

Evidence

package.jsonnpm-shrinkwrap.jsonindex.jsREADME.md

Network endpoints1

artifacts.yosiroute.com/npm/flag-serial-object-syntax

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-13369

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in kepler (npm)

Details

kepler@2.0.999 declares its only runtime dependency, flag-serial-object-syntax, as an HTTP URL to a third-party host (https://artifacts.yosiroute.com/npm/flag-serial-object-syntax) rather than a version resolved from the npm registry, and the shrinkwrap marks that dependency with hasInstallScript: true. Running `npm install kepler` fetches an unpinned, unverified tarball from artifacts.yosiroute.com and executes its lifecycle scripts on the installer's machine. The URL carries no version and no integrity metadata, so its contents can change at any time under the third-party host's control. The kepler package itself has placeholder metadata (author `Package Registry`, repository `github.com/example/...`) unrelated to the yosiroute.com host, and ships no first-party code that would justify sourcing a dependency off-registry. The dependency-tree-hijack shape — an off-registry, mutable, install-scripted tarball pulled in transitively — means any code the operator of artifacts.yosiroute.com serves runs with the privileges of the installer on `npm install`.

References

OSV advisory PACKAGE PACKAGE PACKAGE PACKAGE PACKAGE PACKAGE

Decision evidence

public snapshot

AI called this Suspicious at 93.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for block

package.json pins dependency to a non-registry URL.
npm-shrinkwrap.json marks that dependency hasInstallScript.
Lockfile has no integrity hash for the fetched dependency.
Package manifest version conflicts with shrinkwrap/README 1.0.0 metadata.

Evidence against

package.json defines no lifecycle scripts.
index.js only exports static name/version data.
No package source reads files, env, credentials, or invokes network/shell APIs.

Behavioral surface

SourceNo risky source behavior triggered.

Supply chain

Trivial

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 62 B of source

Source & flagged code

1 flagged

package.jsonView file

•Published source reference

High

Suspicious Dependency Evidence

package.json pins dependency to a non-registry URL.

package.jsonView on unpkg

Source & flagged code

1 flagged · loading source

package.jsonView file

•Published source reference

High

Suspicious Dependency Evidence

package.json pins dependency to a non-registry URL.

package.jsonView on unpkg

Findings

4 High

HighSuspicious Dependency Evidencepackage.json

HighSuspicious Dependency Evidence

HighAi Review Evidence