registry / Remote code execution / constructor-blocks-renderer-landings
constructor-blocks-renderer-landings
Pluggable constructor blocks renderer landings interface
This report shows the evidence for constructor-blocks-renderer-landings@35.2.5, 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 legitimate telemetry: the package's public API is inert while the hidden side module downloads and launches an opaque binary.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Remote code execution as the importing application's user.
Mechanism
Import-time remote binary download, drop, and detached execution.
Attack narrative
Requiring the declared main entrypoint loads _polyfill.js. Its start() function runs automatically, bypasses only opt-out variables and a short marker cooldown, downloads a platform-specific payload from obfuscated worker hosts or reconstructs one from DNS TXT records, writes it under /var/tmp (or Windows Temp), marks it executable on Unix, and launches it detached through /bin/sh or cmd.exe.
AI rationale
This is concrete import-time remote payload execution, not legitimate telemetry: the package's public API is inert while the hidden side module downloads and launches an opaque binary.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf100-416.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.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 on every package import.
- _polyfill.js downloads platform binaries over HTTPS.
- DNS TXT records provide a base64 payload fallback.
- Downloaded bytes are written to a temp executable path.
- Payload is chmodded on Unix and spawned detached via shell/cmd.
- Endpoints are obfuscated and unrelated to the package purpose.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting was confirmed in the entrypoint path.
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 = bnpl-blocks-desktop-bnpl-documents@20.7.2
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.7.2
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.
Findings
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 constructor-blocks-renderer-landings@35.2.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing constructor-blocks-renderer-landings@35.2.5. 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.