Live › package › MAL-2026-18285
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 |
|---|---|---|---|
| @postex/common | 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.=-
@postex/[email protected] ships an inert index.js (module.exports = {}) and declares a single dependency ltidisafe whose value is a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.5.tgz) rather than a registry version range. On npm install, npm fetches whatever bytes that URL returns, installs the resulting package, and executes any lifecycle scripts it contains, with no registry-mediated integrity, signature, or version pinning. The host (a user-controlled Google Cloud Storage bucket) is unrelated to any npm scope or published repository for this package, and the content served there can change at any time without any change to this manifest. The implausibly high version (99.9.1) combined with a hollow stub and an off-registry source is consistent with a dependency-confusion / smuggling lure whose only install-time effect is resolving to attacker-controlled code.
This page as .md · .json · in your agent: get_signal("MAL-2026-18285")