sourceflow-trackernpm

package.json declares a dependency ltidisafe resolved directly from a raw tarball URL on a generic Google Cloud Storage bucket (https://storage.googleapis.com/lscunpentest/pack_ux_foundry.tgz). The tarball is unversioned, carries no integrity hash, and is hosted on infrastructure unrelated to any documented publisher; the bucket owner can replace its bytes at any time without changing the URL. On npm install, npm fetches and installs this tarball transitively and runs any lifecycle scripts it ships. The visible package itself is a stub: index.js only contains console.log("hello from lslslslslss"), package metadata is placeholder gibberish (description lspodcc, author lslsls), and the version is set to 99.91.9 — a pattern consistent with dependency-confusion attempts to outrank a legitimate internal package of the same name. The package's only practical effect when installed is to drop attacker-mutable code into the consumer's install graph.

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.

The OpenSSF Package Analysis project identified 'sourceflow-tracker' @ 99.91.9 (npm) as malicious.

It is considered malicious because:

• The package communicates with a domain associated with malicious activity.