registry / Remote code execution / tinkoff-boxy-desktop-features-banner

tinkoff-boxy-desktop-features-banner

Internal tinkoff boxy desktop features banner module for platform services

This report shows the evidence for tinkoff-boxy-desktop-features-banner@20.2.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

This is a concrete import-time remote-code-execution chain, not ordinary telemetry. The absence of npm lifecycle hooks does not mitigate activation through the package main entrypoint.

Static reason

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

Trigger

Any application or tool that requires/imports index.js.

Impact

Arbitrary attacker-hosted native code can execute with the importing process's privileges.

Mechanism

Import-time remote payload download, temp-file drop, chmod, and detached execution.

Attack narrative

Requiring index.js silently loads setup.js. That code selects an OS-specific asset path, downloads an opaque payload from rotating workers.dev hosts or reconstructs one from DNS TXT records, writes it to a temporary location, makes it executable on Unix, and launches it detached through /bin/sh or cmd.exe. The same downloader/executor pattern is also present in lib/telemetry.js.

AI rationale

This is a concrete import-time remote-code-execution chain, not ordinary telemetry. The absence of npm lifecycle hooks does not mitigate activation through the package main entrypoint.

Evidence

package.jsonindex.jssetup.jslib/telemetry.js/tmp/.analytics_state/var/tmp

Network endpoints8

oob-worker.cf99-9b3.workers.devoob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devtin.dl.well1.sitetina.dl.well1.site

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 ./setup at module load.
setup.js downloads platform binaries from rotating workers.dev hosts.
setup.js falls back to DNS TXT payload retrieval from well1.site.
setup.js writes payloads to temp storage, chmods non-Windows files, then spawns them detached via shell.
No lifecycle hook is needed: requiring the declared main activates the chain.

Evidence against

package.json contains no lifecycle scripts.
The exported banner class itself is inert, but its import-time side effect is not.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.8 KB of source

Source & flagged code

5 flagged

lib/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 · L27

495L496: fork() { L497: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L495

•matchType = normalized_sha256 matchedPackage = sme-crm-services-sme-crm-services-core@20.1.4 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:20.1.4 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.jsView on unpkg

Low

Weak Crypto

Package source references weak cryptographic algorithms.

lib/telemetry.jsView on unpkg · L27

setup.jsView file

4Trigger-reachable chain: manifest.main -> index.js -> setup.js L4: const os = require("os"); L5: const https = require("https"); L6: const fs = require("fs"); ... L46: const MAX_AGE = 21466; L47: const _l = (...a) => process.stderr.write(""); L48: ... 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"); ... L91: try { L92: require("dns").resolveTxt(d, (e, rr) => { L93: 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.

setup.jsView on unpkg · L4

Source & flagged code

5 flagged · loading source

lib/telemetry.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

495L496: fork() { L497: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L495

High

Known Malware Source Similarity

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

Findings

2 Critical2 High3 Medium3 Low

CriticalDownload Executelib/telemetry.js

CriticalTrigger Reachable Dangerous Capabilitysetup.js

HighChild Processlib/telemetry.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowWeak Cryptolib/telemetry.js

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

This report applies to tinkoff-boxy-desktop-features-banner@20.2.4.

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

Avoid installing tinkoff-boxy-desktop-features-banner@20.2.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:16:49.482Z (UTC).

Source advisory published: 2026-08-05 01:32:48.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:12 PM 20.2.4shownMaliciousRemote Code ExecutionBlockPublishedAug 2, 2026, 10:17 AM

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