Malicious code in kepler (npm)

__

Source: amazon-inspector (672a1c042704318fe56d5da08c0f1d20b404274bd6ad339efc2f1c581d869d77)

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.

Source: ghsa-malware (3e9c8ce334283800aaf7e327561dde2f9e8a54a897457868b99e7c0efd2d7912)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.