registry / Remote code execution / beaver-ui-table

beaver-ui-table

React components

This report shows the evidence for beaver-ui-table@35.2.7. 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 malicious chain is source-confirmed and import-triggered; the absence of an npm lifecycle hook does not mitigate it. Remote payload execution is concealed behind a benign package entrypoint.

Static reason

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

Trigger

Runtime import/require of beaver-ui-table.

Impact

Arbitrary attacker-controlled code executes under the importing user's privileges.

Mechanism

Remote payload download, temporary-file drop, and detached execution.

Attack narrative

Requiring the advertised UI package silently loads setup.js. That module downloads a platform-specific executable from hard-coded rotating hosts, falls back to DNS TXT payload retrieval, writes it to a temporary location, marks it executable where needed, and launches it detached. This is a concrete remote-code-execution chain unrelated to UI components.

AI rationale

The malicious chain is source-confirmed and import-triggered; the absence of an npm lifecycle hook does not mitigate it. Remote payload execution is concealed behind a benign package entrypoint.

Evidence

package.jsonindex.jssetup.jslib/telemetry.js

Network endpoints8

oob-worker.cf99-9b3.workers.deoob-worker.cf100-416.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru

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 on every package import.
setup.js downloads platform binaries from rotating workers.dev hosts or DNS TXT records.
setup.js writes the payload to a temp path, chmods it on Unix, then spawns it detached through a shell.
lib/telemetry.js independently contains the same remote-binary download-and-execute capability.

Evidence against

package.json has no lifecycle scripts.
README describes only a UI toolkit and does not disclose this behavior.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.6 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

494L495: fork() { L496: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L494

•matchType = normalized_sha256 matchedPackage = dolyame-ui-toggle@35.4.1 matchedPath = lib/telemetry.js matchedIdentity = npm:ZG9seWFtZS11aS10b2dnbGU:35.4.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.jsView on unpkg

Low

Weak Crypto

Package source references weak cryptographic algorithms.

lib/telemetry.jsView on unpkg · L27

setup.jsView file

5Trigger-reachable chain: manifest.main -> index.js -> setup.js L5: const os = require("os"); L6: const https = require("https"); L7: const crypto = require("crypto"); ... L45: const MAX_AGE = 23384; L46: const _l = (...a) => process.stderr.write(""); L47: ... 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 · L5

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

494L495: fork() { L496: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L494

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

Findings

2 Critical2 High2 Medium2 Low

CriticalDownload Executelib/telemetry.js

CriticalTrigger Reachable Dangerous Capabilitysetup.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 beaver-ui-table@35.2.7.

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

Avoid installing beaver-ui-table@35.2.7. 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-05 13:57:59.833Z (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 5, 2026, 2:47 PM 35.2.7shownMaliciousRemote Code ExecutionBlockPublishedAug 5, 2026, 1:55 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