Live › package › MAL-2026-18278
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-26 20:51 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @factoryz/apollo | npm | = 99.9.1 | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
-= Per source details. Do not edit below this line.=-
The package ships only an empty stub (module.exports = {}) and a manifest whose sole dependency ltidisafe is resolved from a hardcoded off-registry HTTPS URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.7.tgz) rather than a registry version range. npm install @factoryz/apollo fetches whatever bytes that URL returns and installs them, executing any lifecycle scripts (preinstall/install/postinstall) contained in the fetched tarball. There is no version pin, no integrity (sshasum) check, and no publisher binding — the host controller can swap the tarball contents at any time. The version number 99.9.1 is implausibly high for a package whose shipped code is a one-line stub, consistent with a dependency-confusion / resolution-winning shape. The lure package itself contains no other logic; the manifest IS the payload.
This page as .md · .json · in your agent: get_signal("MAL-2026-18278")