registry / Remote code execution / beaver-ui-list
beaver-ui-list
visual components
This report shows the evidence for beaver-ui-list@35.4.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-aiThe reachable import-time loader executes opaque remotely controlled binaries without user action or package-aligned purpose. Absence of lifecycle hooks does not mitigate the import-time execution path.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of beaver-ui-list through index.js.
Impact
Arbitrary attacker-controlled code can execute under the importing process's user account.
Mechanism
Remote payload download or DNS retrieval followed by detached native execution.
Attack narrative
The package main file catches and suppresses errors while requiring _ext.js. That module selects a platform payload, downloads it from obfuscated hosts or reconstructs it through DNS TXT records, writes it to a temporary executable path, makes it executable on Unix, and launches it detached through /bin/sh or cmd.exe. This is concrete staged remote code execution during ordinary package import.
AI rationale
The reachable import-time loader executes opaque remotely controlled binaries without user action or package-aligned purpose. Absence of lifecycle hooks does not mitigate the import-time execution path.
Evidence
package.jsonindex.js_ext.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.c101-adf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packagesdk.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 ./_ext on every package import.
- _ext.js downloads platform-specific binaries over HTTPS.
- _ext.js falls back to DNS TXT payload retrieval.
- _ext.js writes a downloaded binary, chmods it, then launches it detached via shell/cmd.
- _ext.js hides errors and uses a temporary cooldown marker.
Evidence against
- package.json has no lifecycle scripts.
- No credential or user-file harvesting is present in the reachable loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_ext.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const COOLDOWN = 21421;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: if (e || !rr || !rr.length) return r("");
Critical
4Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L4: const os = require("os");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const COOLDOWN = 21421;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: 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.
_ext.jsView on unpkg · L4116try {
L117: const cp = require("child_process");
L118: if (isWin) {
Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to beaver-ui-list@35.4.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing beaver-ui-list@35.4.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.