registry / Remote code execution / beaver-ui-popover-card
beaver-ui-popover-card
UI toolkit
This report shows the evidence for beaver-ui-popover-card@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-aiThis is concrete import-time remote payload execution unrelated to the advertised UI toolkit. No lifecycle hook is needed because the package main entrypoint reaches the bootstrapper.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of the package main entrypoint.
Impact
Arbitrary remote code execution under the importing user's privileges.
Mechanism
remote payload download, drop, chmod, and detached execution
Attack narrative
The public entrypoint silently requires _support.js. On import, it selects a platform payload URL, retrieves a binary from rotating external hosts or reconstructs one through DNS TXT records, stores it in a temporary directory, marks it executable on Unix, and starts it detached. The temporary state file merely limits repeated execution.
AI rationale
This is concrete import-time remote payload execution unrelated to the advertised UI toolkit. No lifecycle hook is needed because the package main entrypoint reaches the bootstrapper.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf101-adf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.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 _support.js on every package import.
- _support.js downloads platform binaries from worker hosts.
- Downloaded bytes are written to /var/tmp or Windows Temp and made executable.
- _support.js launches the downloaded file detached via shell/cmd.
- DNS TXT fallback reconstructs a binary payload from dl.wel1.ru domains.
- The behavior is silent and only throttled by a temporary state file.
Evidence against
- package.json contains no lifecycle scripts.
- The exported UI class in index.js is otherwise minimal.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
2L3: const https = require("https");
L4: const fs = require("fs");
...
L45: const TTL = 23090;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: 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.
_support.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _support.js
L2:
L3: const https = require("https");
L4: const fs = require("fs");
...
L45: const TTL = 23090;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: 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.
_support.jsView on unpkg · L2119try {
L120: const cp = require("child_process");
L121: if (isWin) {
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to beaver-ui-popover-card@35.4.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing beaver-ui-popover-card@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.