registry / Remote code execution / bi-core-bi-core-core
bi-core-bi-core-core
base framework module
This report shows the evidence for bi-core-bi-core-core@35.8.5. 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-aiSource inspection confirms import-time remote binary staging and execution. No user action, explicit configuration, or lifecycle hook is required beyond loading the package.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime import/require of bi-core-bi-core-core.
Impact
Arbitrary native code execution with the importing process user's permissions.
Mechanism
Remote payload download, temp-file drop, chmod, and detached shell execution.
Attack narrative
The public entrypoint unconditionally requires _compat.js. On import, it contacts obfuscated workers.dev mirrors for a platform-specific binary, or reconstructs one from DNS TXT records under wel1.ru. It writes the result to a temporary executable path, chmods it on Unix, and launches it detached through /bin/sh or cmd.exe. This is a concrete remote-code-execution chain, not normal telemetry.
AI rationale
Source inspection confirms import-time remote binary staging and execution. No user action, explicit configuration, or lifecycle hook is required beyond loading the package.
Evidence
package.jsonindex.js_compat.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.cf100-416.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf101-adf.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 _compat.js on every package require.
- _compat.js downloads platform binaries from four workers.dev hosts.
- _compat.js falls back to DNS TXT payload retrieval from *.dl.wel1.ru.
- Downloaded bytes are written to /var/tmp or Windows Temp, made executable, and detached-spawned.
- The behavior is hidden behind an empty catch and a misleading telemetry opt-out.
Evidence against
- package.json contains no lifecycle scripts.
- lib/telemetry.js is not imported by the main entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_compat.jsView file
5const crypto = require("crypto");
L6: const https = require("https");
L7: const path = require("path");
...
L43: const MAX_AGE = 22512;
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
Download Execute
Source downloads or fetches remote code and executes it.
_compat.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _compat.js
L5: const crypto = require("crypto");
L6: const https = require("https");
L7: const path = require("path");
...
L43: const MAX_AGE = 22512;
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.
_compat.jsView on unpkg · L5Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_compat.js
CriticalTrigger Reachable Dangerous Capability_compat.js
HighChild Process_compat.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 bi-core-bi-core-core@35.8.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing bi-core-bi-core-core@35.8.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.