devplatform-spa-route-tree
Devplatform spa route tree SDK for internal consumers
This report shows the evidence for devplatform-spa-route-tree@35.1.3, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe import-time, unverified remote payload execution chain is concrete and complete in _loader.js. Absence of lifecycle scripts does not mitigate runtime execution when consumers import the package.
Decision evidence
public snapshot- index.js imports _loader.js on every package require.
- _loader.js downloads platform binaries over HTTPS and DNS TXT.
- _loader.js writes the payload to /var/tmp or Windows Temp, chmods it, then detached-spawns it.
- No checksum, signature, or trusted payload verification is present.
- README describes only a route-tree interface, not binary downloading or execution.
- package.json has no lifecycle scripts.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to devplatform-spa-route-tree@35.1.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing devplatform-spa-route-tree@35.1.3. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.