registry / Remote code execution / devplatform-spa

devplatform-spa

Shared devplatform spa library for backend integration

This report shows the evidence for devplatform-spa@35.1.4. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.

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-ai

The package contains a concrete, stealthy import-time downloader and executor of remote native payloads. The absence of an npm lifecycle hook does not mitigate runtime compromise when consumers import the declared main entrypoint.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Any runtime require/import of devplatform-spa

Impact

Arbitrary attacker-controlled native code executes with the importing process's privileges.

Mechanism

remote binary download, temporary-file drop, and detached shell execution

Attack narrative

index.js loads _loader.js whenever the package is imported. The loader contacts shuffled Workers hosts for an OS-specific payload, with DNS TXT reconstruction as a fallback; it then writes the received bytes to a temporary file, marks Unix files executable, and launches them in a detached hidden process. This is an import-time remote-code-execution chain.

AI rationale

Evidence

package.jsonindex.js_loader.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe

Network endpoints7

oob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/package

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js imports _loader.js automatically on package import.
_loader.js downloads platform binaries from three oob-worker*.workers.dev hosts.
DNS TXT fallback reconstructs binary data from wel1.ru domains.
Downloaded bytes are written under /var/tmp or Windows Temp, made executable, and detached-spawned.
Execution is hidden with ignored stdio and empty stderr logging.

Evidence against

package.json has no lifecycle scripts.
No credential harvesting or AI-agent configuration mutation was found.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.4 KB of source

Source & flagged code

4 flagged

_loader.jsView file

3const crypto = require("crypto"); L4: const https = require("https"); L5: const path = require("path"); ... L44: const TTL = 20770; L45: const _l = (...a) => process.stderr.write(""); L46: ... L57: const isWin = _p("platform") === "win32"; L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L92: try { L93: require("dns").resolveTxt(d, (e, rr) => { L94: if (e || !rr || !rr.length) return r("");

Critical

Download Execute

Source downloads or fetches remote code and executes it.

_loader.jsView on unpkg · L3

3Trigger-reachable chain: manifest.main -> index.js -> _loader.js L3: const crypto = require("crypto"); L4: const https = require("https"); L5: const path = require("path"); ... L44: const TTL = 20770; L45: const _l = (...a) => process.stderr.write(""); L46: ... L57: const isWin = _p("platform") === "win32"; L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L92: try { L93: require("dns").resolveTxt(d, (e, rr) => { L94: if (e || !rr || !rr.length) return r("");

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

_loader.jsView on unpkg · L3

120try { L121: const cp = require("child_process"); L122: if (isWin) {

High

Child Process

Package source references child process execution.

_loader.jsView on unpkg · L120

•matchType = token_shingles matchedPackage = dolyame-boxy-independent-bnpl-separator@35.2.6 matchedPath = _platform.js matchedIdentity = npm:[redacted]:35.2.6 similarity = 0.833 shingleOverlap = 40 summary = source token shingles overlapped finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

_loader.jsView on unpkg

Source & flagged code

4 flagged · loading source

_loader.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

_loader.jsView on unpkg · L3

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

_loader.jsView on unpkg · L3

Findings

2 Critical2 High2 Medium1 Low

CriticalDownload Execute_loader.js

CriticalTrigger Reachable Dangerous Capability_loader.js

HighChild Process_loader.js

HighKnown Malware Source Similarity_loader.js

MediumNetwork

MediumEnvironment Vars

LowFilesystem

Affected versions and remediation

This report applies to devplatform-spa@35.1.4.

The versions list below shows the verdict for each recorded version.

Avoid installing devplatform-spa@35.1.4. 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: 2026-08-26 01:18:19.495Z (UTC).

Source advisory published: 2026-08-05 13:44:30.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedAug 25, 2026, 3:56 PM 35.1.4shownMaliciousRemote Code ExecutionBlockPublishedAug 5, 2026, 1:35 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Source & flagged code

Related packages

Other remote code execution packages