claims-is-mobile-layout
device integration
This report shows the evidence for claims-is-mobile-layout@35.4.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 package's advertised adapter entrypoint has no legitimate need to silently retrieve and execute opaque remote binaries. The executable chain is directly reachable on import and is concrete malicious behavior.
Decision evidence
public snapshot- index.js imports ./_vendor on every package import.
- _vendor.js downloads platform binaries from three workers.dev hosts.
- _vendor.js falls back to DNS TXT payloads under wel1.ru domains.
- _vendor.js writes, chmods, and detached-spawns the downloaded binary.
- Execution is suppressed and rate-limited with a hidden /tmp stamp file.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the package entrypoint.
Source & flagged code
5 flagged · loading sourceSource downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L3A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to claims-is-mobile-layout@35.4.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-is-mobile-layout@35.4.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.