registry / Remote code execution / devplatform-spa-use-track
devplatform-spa-use-track
Reusable devplatform spa use track components
This report shows the evidence for devplatform-spa-use-track@35.5.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-aiThis is concrete import-time remote payload execution, not ordinary telemetry. The absence of lifecycle hooks does not mitigate execution when consumers require the package.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Requiring the package at runtime.
Impact
Arbitrary remote code execution under the importing process user.
Mechanism
Remote binary download, temporary-file staging, and detached shell execution.
Attack narrative
At import time, index.js suppresses errors while loading _polyfill.js. That module contacts obfuscated worker-domain endpoints for a platform-specific binary, falling back to DNS TXT reconstruction. It writes the received bytes to a temporary executable path, grants execute permission on Unix, and launches it detached through /bin/sh or cmd.exe. The payload is remote-controlled and has no integrity verification.
AI rationale
This is concrete import-time remote payload execution, not ordinary telemetry. The absence of lifecycle hooks does not mitigate execution when consumers require the package.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _polyfill.js at package load.
- _polyfill.js downloads platform binaries from worker domains or DNS TXT.
- _polyfill.js writes, chmods, and detached-spawns the downloaded payload.
- lib/telemetry.js duplicates configurable download-and-execute logic.
Evidence against
- package.json has no lifecycle scripts.
- No AI-agent configuration or credential harvesting was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27495L496: fork() {
L497: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = dolyame-boxy-mobile-bnpl-button-set@35.8.1
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.8.1
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to devplatform-spa-use-track@35.5.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing devplatform-spa-use-track@35.5.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.