registry / Malware / kepler

kepler

This report shows the evidence for kepler@99.99.99. 11 of 12 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.

This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.

OpenSSF/OSV Malicious Advisory

imported 3mo ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-13369 confirms this npm version as malicious.

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

OpenSSF/OSV advisory PACKAGE PACKAGE PACKAGE PACKAGE PACKAGE PACKAGE PACKAGE

Independent LPM AI assessment

Suspicious

Independent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.

kepler contains no direct malicious code, but it deliberately pins an opaque remote dependency that is declared to execute during installation. This is a concrete unresolved install-time payload risk.

Static reason

No blocking static signals were detected.

Trigger

npm installation

Impact

Unverified install-time code may run from the remote dependency.

Mechanism

remote dependency with declared install hook

AI rationale

Evidence

package.jsonnpm-shrinkwrap.jsonindex.jsREADME.md

Network endpoints1

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

Independent scan evidence

public snapshot

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

Evidence for AI warning decision

package.json declares a direct dependency from artifacts.yosiroute.com.
npm-shrinkwrap.json marks that remote dependency hasInstallScript: true.
The installed dependency source is absent, so its install behavior cannot be verified.

Evidence against

package.json has no package lifecycle scripts.
index.js only exports static name/version data.
No package-owned file/network/child-process behavior was found.

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 declares a direct dependency from artifacts.yosiroute.com.

package.jsonView on unpkg

Source & flagged code

1 flagged · loading source

package.jsonView file

•Published source reference

High

Suspicious Dependency Evidence

package.json declares a direct dependency from artifacts.yosiroute.com.

package.jsonView on unpkg

Findings

3 High

HighSuspicious Dependency Evidencepackage.json

HighSuspicious Dependency Evidence

Affected versions and remediation

This report applies to kepler@99.99.99.

The versions list below shows the verdict for each recorded version.

Avoid installing kepler@99.99.99. 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-08-05 19:35:05.999Z (UTC).

Source advisory published: 2026-08-05 18:27:24.000Z (UTC).

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

Versions

12 known versions

0.0.1-securitylatestClean—AllowPublishedAug 20, 2026, 1:07 PM 99.99.99shownMaliciousMalwareBlockPublishedJul 30, 2026, 3:22 AM 5.999.999MaliciousRemote Code ExecutionBlockPublishedJul 30, 2026, 3:17 AM 5.0.999MaliciousMalwareBlockPublishedJul 30, 2026, 3:12 AM

OpenSSF/OSV Malicious Advisory

Independent LPM AI assessment

Independent scan evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Source & flagged code

Related packages

Other malware packages