registry / kepler / 5.999.999

kepler@5.999.999

Generated package

AI Security Review

scanned 16d ago · by lpm-firewall-ai

Installing kepler fetches an unauditable remote dependency whose lock entry declares an install script. That script can execute automatically during dependency installation.

Static reason

No blocking static signals were detected.

Trigger

npm installation of kepler

Impact

Remote publisher-controlled code execution on the installer host.

Mechanism

remote dependency install-script execution

Attack narrative

The manifest redirects dependency resolution to artifacts.yosiroute.com rather than a normal registry package. Its shrinkwrap declares the fetched package has an install script, so npm installation can execute remote-controlled code not included in this package for review. The high published version also conflicts with the embedded 1.0.0 metadata.

Rationale

The package is a minimal carrier for an unauditable remote dependency that automatically executes installation code. Static exports are benign but do not mitigate the install-time execution path.

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 Malicious at 94.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json pins dependency to a non-registry URL.
npm-shrinkwrap.json marks that remote dependency hasInstallScript.
The remote dependency has no integrity hash or bundled source to audit.
Manifest/package sources disagree on version (5.999.999 vs 1.0.0).

Evidence against

index.js only exports static name and version.
No direct lifecycle script or network code exists in package files.

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