@factoryz/apollo
This report shows the evidence for @factoryz/apollo@99.9.1, the only known version.
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.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe dependency’s preinstall hook automatically discloses identifying host and user data to an unrelated fixed collector. This is an unconsented installation beacon, so publication should be blocked.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation of the ltidisafe dependency triggers its preinstall script.
Impact
The collector receives identifying host and user data without installer consent.
Mechanism
The script encodes the hostname, home directory, and username as hexadecimal values, places each in a subdomain of a fixed collector, and calls a helper that makes an HTTP GET request.
Attack narrative
Installing this package installs a remote tarball dependency. Its preinstall hook runs code that encodes the machine hostname, home directory, and username and sends them in HTTP requests to a fixed OAST collector.
AI rationale
The dependency’s preinstall hook automatically discloses identifying host and user data to an unrelated fixed collector. This is an unconsented installation beacon, so publication should be blocked.
Evidence
package.json.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/package.json.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/test.js.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/index.js
Network endpoints1
*.factoryz.apollo.2wz381vbb1cw7nrxxz9akm51fslj9bx0.oastify.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json adds the remote ltidisafe tarball dependency.
- ltidisafe runs test.js automatically in its preinstall hook.
- test.js hex-encodes the hostname, home directory, and username, then passes each value into a request URL under a fixed OAST domain.
- index.js sends the supplied URL using an HTTP GET request.
Evidence against
Behavioral surface
Trivial
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
10"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.7.tgz"
},
"author": "",
"lice
High
Suspicious Dependency Evidence
package.json adds the remote ltidisafe tarball dependency.
package.jsonView on unpkg · L10•Remote tarball dependency specs: ltidisafe@https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.7.tgz
Medium
Remote Tarball Dependency
Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkg.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/package.jsonView file
7"preinstall": "node test.js > /dev/null 2>&1",
"test": "echo \"Error: no test specified\" && exi
High
Findings
6 High1 Medium1 Low
HighSuspicious Dependency Evidencepackage.json
HighSuspicious Lifecycle Evidence.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/package.json
HighAi Review Evidence.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/test.js
HighAi Review Evidence.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/test.js
HighAi Review Evidence.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/test.js
HighAi Review Evidence.lpm-dependency-evidence-6113a965-e362-4cb0-a008-5e20c64e72ce/0/npm-linux/index.js
MediumRemote Tarball Dependencypackage.json
LowScripts Present
Affected versions and remediation
This report applies to @factoryz/apollo@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @factoryz/apollo@99.9.1. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.