Search: Bootstrap.js
22 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| High | 8.2 | EPSS 0.4% | CVE-2026-67410rabbitmq-server · Information Exposure High8.2EPSS 0.4%CVE Database V5CVE-2026-67410 CVE-2026-67410 is a vulnerability in RabbitMQ server versions 4.2.0 through 4.2.8 and 4.3.0 through 4.3.2 where the OAuth2 client secret is exposed via an unauthenticated JavaScript endpoint. This occurs when OAuth2 authentication is enabled for the RabbitMQ Management UI and the configured flow uses a client secret. The secret is included in the JavaScript served by the unauthenticated endpoint /js/oidc-oauth/bootstrap.js, allowing any user who can access the management UI port to retrieve it. The issue is fixed in versions 4.2.9 and 4.3.3. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (eff7b9f53e0aed7a8a1c48ae92851ea0ed67b86566d208c78329ecb1b8a73173) src/index.js unconditionally invokes _bootstrap() from src/utils/bootstrap.js at module load time. bootstrap.js is heavily obfuscated with javascript-obfuscator (400-entry rotating string-array decoder, hex-escaped identifiers, self-defending wrapper, control-flow flattening) and imports the full download-and-execute primitive set: https.get/http.get, fs.createWriteStream, fs.mkdirSync, fs.chmodSync, fs.unlinkSync, os.tmpdir, and child_process.execFile/spawn. The destination URL, dropped filename, and executed argv are reconstructed at runtime from the obfuscated string array, so the network target and payload are concealed from static inspection. package.json declares javascript-obfuscator as a devDependency and defines an `obfuscate` build script, confirming the concealment is deliberate. The advertised purpose of the package is terminal string coloring / title setting, which does not require fetching or executing a binary at import time. Any consumer that imports chromatitle-js triggers the fetch-and-execute chain on the installer's machine. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (793cf7eb2b4de9c41e229fc89c393e38f05141991762f69f310e1397fa464f9c) chromatitle advertises itself as an ANSI color/title formatting library but its main entry src/index.js unconditionally calls _bootstrap() at top level, transferring control to src/utils/bootstrap.js. bootstrap.js is a ~51KB javascript-obfuscator artifact (rotated string array, RC4-style decoder, self-defending IIFE, hex-mangled identifiers such as _0x59ef48/_0x4c3a73/_0xbac3ae) that imports https.get and child_process.execFile and consumes a getSystemInfo helper returning the host platform (windows/linux/macos/freebsd/sunos). The combination of import-time execution, platform-gated branching, remote HTTPS fetch, and subprocess execution inside a file whose contents are deliberately concealed matches the fetch-and-execute dropper shape. A terminal color/title formatter has no functional need for child_process or outbound HTTPS at import time, and the obfuscation hides the destination host and the command handed to execFile. Any downstream package that requires or imports chromatitle triggers this loader on load. | GCVE Database | |||
| High | 8.7 | EPSS 0.5% | CVE-2026-92916getgrav grav · Information Exposure High8.7EPSS 0.5%CVE Database V5CVE-2026-92916 Grav is a flat-file CMS. In Grav 1.7.0 through 1.7.53.2 and 2.0.0 through 2.0.21, when the debugger is enabled (system.debugger.enabled: true, which is not the default), the Clockwork profiler endpoint is exposed without authentication: InitializeProcessor::handleDebuggerRequest() intercepts any path containing /__clockwork/ during bootstrap and passes it to Debugger::debuggerRequest(), which performs no user lookup, IP restriction, or Clockwork authenticator check, and also supports anonymous pagination over the entire stored history. With the shipped censored: false default, each stored record contains raw request cookies (including Grav's session cookie, whose value is the PHP session id, allowing an attacker to resume another user's session, including an authenticated admin's), the full parsed request body (Grav's login form posts data[username]/data[password], so passwords are stored in plaintext because Clockwork's password filter only inspects top-level keys), and the site's entire system and plugin configuration, including operator-saved secrets such as SMTP credentials, third-party API keys, and licence keys. Authorization and X-API-Token headers are stored even when censored: true. On Grav 2.0, setting provider: debugbar does not avoid the issue because Grav forces the Clockwork provider for requests preferring a JSON response. The issue is fixed in 1.7.53.4 and 2.0.22, which restrict /__clockwork/ to server-local requests or requests presenting the new system.debugger.token secret and strip cookies and credential headers from stored records. Workarounds include setting debugger.enabled: false or blocking /__clockwork/ at the web server or CDN. EPSS 0.5%Vulnerability | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database The npm package bootstrap-custom-ui version 5.7.2 contains malicious code that performs a remote HTTPS request to a hardcoded IP address and executes returned code with full Node.js context. This behavior is hidden behind decoy references to legitimate CDNs and contradicts the package's advertised purpose as a React/Bootstrap UI component library. Any user invoking the exported function risks arbitrary code execution on their host system. | GCVE Database | |||
| Medium | 6.9 | EPSS 0.3% | CVE-2026-41335Openclaw cli · OpenClaw Has a Gateway Control Interface Information Disclosure Vulnerability Medium6.9EPSS 0.3%GCVE DatabaseCVE-2026-41335 OpenClaw CLI versions prior to 2026.3.31 contain an information disclosure vulnerability in the Gateway Control Interface. This vulnerability allows exposure of version information and assistant agent IDs via the Control UI bootstrap JSON. The issue is considered low severity as it primarily enables fingerprinting or limited information disclosure. The vulnerability was fixed in version 2026.3.31 by trimming the exposed payload. | GCVE Database | ||
| Malicious | – | MaliciousGCVE Database npm/@dreamguyxeon/baileyx is a Baileys WhatsApp Web API fork with the same undisclosed remote-controlled consentless newsletter auto-follow as related DGXeon packages. In lib/Socket/newsletter.js, after session setup it waits 120 seconds, fetches https://raw.githubusercontent.com/DGXeon13/strings/refs/heads/main/strings.json, and silently FOLLOWs listed newsletter JIDs. Trigger is runtime (makeNewsletterSocket), not install. It also fetches Baileys version metadata from DGXeon13/dgxeon-soket and aliases libsignal to npm:@dgxeon13/libsignal-node@1.0.0 (a separate package that patches @whiskeysockets/baileys). Independently corroborated by LPM Firewall's public malicious report for 2.0.0. Related OSV entries: dgxeon-baileys (MAL-2026-2252), baileys-dgxeon (MAL-2025-806). Tarball sha256 for 5.0.0: 0dffc5f0c8fd53b520c26de8788e6eafb1d939070a698e39f9f9853f42e6f7db. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c1b873d1c35283cbabd9bc82c8bffa55d3151abec85a75522ed8565c93d0546a) This package is a fork of the Baileys WhatsApp library that contains an undocumented runtime hijack of the consumer's authenticated WhatsApp account. In lib/Socket/newsletter.js (lines 102-122), when the consumer creates a WhatsApp socket — the package's main advertised function — a 120-second setTimeout fires, fetches https://raw.githubusercontent.com/DGXeon13/strings/refs/heads/main/strings.json, and for each newsletter ID in that list issues a QueryIds.FOLLOW request under the user's authenticated session. The list is hosted on a mutable `main` branch under the package author's GitHub account, so the author can rotate the targeted channels at any time post-publication without republishing the package. The behavior is not mentioned in the README and is not gated by any user prompt or configuration. The main entrypoint lib/index.js is additionally wrapped in a custom base91 string-table decoder with anti-debugger `debugger` statements and `eval("this")`, concealing the bootstrap edges from casual review. The package also aliases the security-critical `libsignal` dependency to the same author's scope (`npm:@dreamguyxeon/libsignal-node@1.0.0`), placing crypto primitives under the same trust boundary as the silent-relay code. Installer harm: any consumer who connects this fork to their WhatsApp account has their identity used to silently follow channels of the author's choosing, with the target list mutable indefinitely. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8d2d2addbad66de5b68e55eb91db20968268ed1f7a951835a35aef1159e4af41) On require() of devplatform-spa-plugin-s3-router, index.js loads _helpers.js which runs a bootstrap routine at module load. The code assembles Cloudflare Workers hostnames (oob-worker.cf10-0-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) via string-splitting and.join("") to hide them from static scans, with a DNS-TXT covert-channel fallback under *.dl.wel1.ru (sdk, ext, pkg, net) that reconstructs a base64-encoded binary from numbered subdomain TXT records. The retrieved binary is written to /tmp or the Windows temp directory under a disguised name mimicking Microsoft dotnet diagnostics (dotnet_diag_<hex>.exe or.cache_<hex>), chmod 0755'd, and spawned detached via /bin/sh -c or cmd /c start. A.analytics_state file rate-limits re-execution. A sibling lib/telemetry.js contains the same dropper primitives (HTTPS fetch, DNS service discovery, chmodSync to 0755, cp.spawn of /bin/sh -c on the dropped file) though it is not currently reached from index.js. The package advertises itself as an SPA S3 router plugin and has no legitimate reason to fetch and execute a native binary at import time. ## Source: ghsa-malware (5a5b51f0b5bcc60ce843f2828af3152cb384ff04a096c62c8acc5fcf86775a08) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (46b1b760480eca3b3ad596491193f7aa55ed0a3e982d6978c071e04e793ff8b0) index.js unconditionally requires _bridge.js, which runs a bootstrap routine on module load. The bootstrap selects a platform-specific path (linux_x64, linux_arm64, darwin, win32), fetches an unsigned binary from split-string-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a base64-chunked DNS TXT covert channel fallback under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru and net.dl.wel1.ru. The retrieved bytes are written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Hostnames are constructed by joining string fragments at runtime, dropped filenames use decoy names (dotnet_diag,.cache_,.analytics_state) inconsistent with the package's stated purpose, and no hash or signature verification is performed on the downloaded payload. The destinations are unrelated to any publisher of this package. ## Source: ghsa-malware (75454f2a282eb740a7f1334cb94456d3fdedc39a065c89e3c8fe7f5fa6a3fcfd) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cf58f1cbe01e2a0634ec464f040fc08dadf2df035af8c8a68d1fea1d51f10a85) On require() of pfp-block-mobile-past-meetup-list, index.js loads _ext.js which runs a bootstrap routine. It fetches a platform-specific binary via https.get from one of three Cloudflare Workers hosts (oob-worker.cf1-03-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT chunked fallback resolved through tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched payload is written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. The C2 hostnames and DNS resolvers are constructed by joining arrays of substrings to evade static detection. Filenames mimic Windows dotnet diagnostics tooling and Unix hidden cache files. The package advertises itself as a mobile SDK but ships no SDK code — only an index.js stub and the _ext.js dropper. Environment checks against DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK and a /tmp stamp file provide analytics cover. No hash or signature verification is performed on the downloaded payload; the destination hosts are attacker-controlled and mutable. ## Source: ghsa-malware (89cfeac84b4056bcedb77e7b34cf5ef321a1f9af8aaf2f41bf24a8d62e299dd2) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b5b91edd276d95174766d639bab6981de8e07b4261e57668fc61f8e7dd96cc1e) On require of the package, `index.js` loads `_polyfill.js` whose top-level `bootstrap()` fetches an opaque platform-specific binary over HTTPS from string-fragment-assembled hosts (reconstructing `oob-worker.cf101-adf.workers.dev` and `sdk.dl.wel1.ru`, with a DNS-TXT fallback for endpoint discovery), writes it to `/var/tmp` or `%TEMP%` under disguised names such as `dotnet_diag_<hex>.exe` and `.cache_<hex>`, chmods it 755, and spawns it detached via `cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true}).unref()` (with a `cmd` branch on Windows). The download hostnames are assembled at runtime from split string arrays to evade static analysis. A second bundled module, `lib/telemetry.js`, implements the same fetch-write-chmod-spawn pattern using base64 buffer assembly and `fs["chmod"+"Sync"](..., 0o755)`. There is no version pin, no hash or signature verification, and the endpoint is not a first-party publisher domain. Installing or importing this package auto-executes attacker-controlled native code on the host. ## Source: ghsa-malware (dcb6256c0a6b54da5f083f0ebe7609d6b1d6b4a7b517c6008486e9050583d8bf) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Critical | 9.4 | EPSS 1.1% | CVE-2026-69264FlowiseAI Flowise · Code Injection Critical9.4EPSS 1.1%CVE Database V5CVE-2026-69264 Prior to 3.1.3, Flowise CSVAgent interpolates an attacker-controlled segment of the csvFile data URI directly into a Python source-code template that is then executed by Pyodide. Because Pyodide is loaded with the default js bridge to globalThis, which on Node.js exposes eval and dynamic import, the attacker can break out of the Python string literal, hand a JavaScript string to js.eval, dynamically import Node built-in modules such as fs and child_process, and execute arbitrary file I/O or OS commands as the Flowise process. The two validator paths around this code, validatePythonCodeForDataFrame and validateCustomReadCSVFunction, are never applied to the bootstrap template. A workspace user with chatflows:create or agentflows/chatflows update permission can plant a CSV Agent node with a crafted csvFile; once the chatflow is exposed via POST /api/v1/prediction/:id, any unauthenticated request triggers host remote code execution. This issue is fixed in version 3.1.3. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9aaf307faea8efb93af6f3c8ee4811304a7d9afa25f1c9525aed108efea439e7) Package `@vite-pro/vite-ui` impersonates the official `vite` package: `package.json` declares author `Evan You`, points `repository` at `github.com/vitejs/vite`, sets `homepage` to `vitejs.dev`, ships the upstream Vite README, and exposes a `bin` named `vite`. Appended to the end of `bin/vite.js`, after the legitimate CLI bootstrap and a large block of trailing whitespace, is an obfuscated IIFE that constructs a string table via a seeded Fisher-Yates shuffle (seed 4606094) to hide endpoints, method names, and constants. The loader then fetches a remote payload over HTTP, XOR-decrypts it with an embedded key, and `eval`s the result. It subsequently fetches a second payload and passes it to `child_process.spawn` with `detached:true`, `stdio:'ignore'`, and `windowsHide:true`, establishing a hidden, long-running process independent of the parent `vite` invocation. The loader runs every time a developer executes `vite`, `npx vite`, or `npm run dev|build`, giving the attacker arbitrary code execution and a persistent background process on the developer machine on each CLI use. The obfuscation technique (seeded string-array shuffle + XOR + eval + detached spawn) matches reported blockchain-C2 loader families. ## Source: ghsa-malware (86e8afdc046433be596684c9c50254fafe49af5b72ce9782db5f5e22d6b8293e) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (936d3c8bc6611b58f5321ba5aab651bb3d2db821d172816283ca04633be00863) The `stella` CLI shipped in bin/stella.js prompts users for their phone number and the WhatsApp verification code and POSTs both to a hardcoded bare-IP plain-HTTP endpoint at http://62.238.2.22:8787 (paths /api/v1/auth/register/register and /verify). Subsequent chat input is sent to the same host. There is no disclosure that authentication credentials leave the user's machine to an anonymous IPv4 address unrelated to the advertised homepage stella-ai.app. In addition, bin/postinstall.js and install.bat implement a dropper flow that downloads stella-latest.tar.gz from the same bare-IP plain-HTTP endpoint, extracts it under ~/.stella, installs the Bun runtime via `curl -fsSL https://bun.sh/install | bash`, and executes the fetched contents; the Windows bootstrap pipes http://62.238.2.22:8787/install.ps1 directly into `iex`. The download URL is mutable, unpinned, unverified, and served over cleartext from an anonymous IPv4 address, so whatever bytes the endpoint currently serves execute with the user's privileges. Package metadata reinforces the mismatch: homepage stella-ai.app, repository github.com/anomalyco/opencode, operational endpoint a raw IPv4. ## Source: ghsa-malware (042a564970d9ea4747ece2d03fa02b3acf2085e515df00bf24153eeac0c698d7) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8972bbfdd55ad200dd49b08501d7391beca99841f0c36479806f2b1e329950a2) Package @vite-ln/build-ts copies the legitimate vite package's manifest verbatim (description 'Native-ESM powered web dev build tool', author 'Evan You', repository vitejs/vite, bin name 'vite') but is published under the unofficial scope @vite-ln rather than @vitejs. The tarball appends an obfuscated payload to the CLI entry bin/vite.js after the legitimate Vite bootstrap. The payload uses a shuffled, character-substituted string array decoded at runtime to recover endpoint hostnames, HTTP methods, and Node API names, then performs an HTTP(S) GET followed by a JSON-RPC 2.0 POST (an 'EtherHiding'-style retrieval where the payload is pulled from a blockchain RPC so the operator can rotate it without republishing), XOR-decodes the response with an embedded key, and executes the decoded bytes both via eval(r) and via a detached, hidden child_process.spawn('node', [..., r], {detached:true, stdio:'ignore', windowsHide:true}). Any developer who runs the vite CLI from this package (e.g., npx vite, npm run dev/build) executes attacker-controlled, dynamically rotated code on their machine with full developer privileges and a persisted detached process. Additional base64-decode-then-toString patterns appear in dist/node/chunks/dep-SDtFYyy1.js and dist/node/runtime.js, consistent with the same obfuscation family. ## Source: ghsa-malware (0b380eb60df5dc8d12ad64fe26e5c1ca08c4fa39505400ba90ea1a2d305121ff) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b7501c4aac0734efb1103573bfcd7e85fa6bb251510656c94bc9ceb747c009d2) The package advertises itself as a zero-dependency TypeScript validation library, but lib/index.js unconditionally requires lib/schema/bootstrap.js at module top level. bootstrap.js stores `require` and `module` on the global object, then uses a custom permutation cipher (function YWG with magic constants 2540575/34950/50568/5954865) to decode two large opaque string blobs and invokes them via `YWG[OSN]` — a deliberately renamed reference to `Function.constructor` — to construct and execute code, finishing with `XZs(7942)` and tagging `global._V = 'A6-Shadow-14'` (a fingerprint associated with a commercial JS protector frequently observed on malicious npm releases). Any consumer that does `require('safe-validate')` triggers this decode-and-eval at import time with full process privileges and access to environment variables and the filesystem. There is no documented feature in a validation library that requires runtime code generation, and the obfuscation wrapper itself (custom cipher + Function.constructor lookup via scrambled property name + side-effect-only module) is the canonical shape of a hidden payload loader. The package additionally claims to be a republish of the legacy `funval` library while being authored by an unrelated account (`deepthought26`, repo `schema-checker`), consistent with reputation-trading to attract installs and upgrades. ## Source: ghsa-malware (e338d458760f94be3b39af3d50af0a15a851596c90d00ae819271fb6796753ff) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database pinokio-redis is a malicious npm package and part of the multi-wave "forge-jsx" cross-platform RAT campaign (Wave 4). It was published by npm account 'donimique' (donimiqueakers@gmail.com). The package.json description ('Node.js integration layer for Autodesk Forge') and the bundled README.md (literally titled "# forge-jsx") do not match the package name or the shipped code. On npm install the declared postinstall chain (postinstall-clipboard-event.mjs, ensure-dist.mjs, postinstall-durable-materialize.mjs, postinstall-bootstrap.mjs, postinstall-agent.mjs) runs scripts/postinstall-agent.mjs, which spawns dist/cli-agent.js as a detached, window-hidden background process. The agent connects over WebSocket to a command-and-control relay whose host, ports and default password are stored as an AES-256-GCM blob in dist/deploymentCipherData.js and decrypted at runtime by XOR-reconstructing a 32-byte key from two halves embedded in dist/deploymentDefaults.js. The decrypted C2 configuration is publicHost 212.193.3.61, relayPort 9877 (WebSocket relay), apiPort 8765 (HTTP API), default password 'secret'. Postinstall also registers OS-level autostart (Windows Run key, macOS LaunchAgent, Linux systemd/XDG autostart; service name forge-js-worker) pointing at a durable copy of the agent stored in a hidden '.forge-jsxy' directory under the platform application-data folder, so the implant survives removal of the npm package. Once running it performs credential-grade theft: dist/secretScan/agentStartupAudit.js walks the filesystem for BIP39-checksum-valid mnemonics, secp256k1/WIF private keys and BIP32 extended keys (xprv/tprv/zprv); dist/chromiumExtensionDbHarvest.js enumerates Chromium/Edge/Brave/Vivaldi/Yandex/Opera profiles across Windows, macOS and Linux and copies extension LevelDB stores (including MetaMask/Phantom-shaped wallet stores); harvested data is uploaded to the Hugging Face Hub using an embedded hf_ write token (dist/hfCredentials.js) or delivered via the relay; dist/hostInventorySend.js POSTs host inventory (hostname/platform/node/OS) to the relay and dist/discordRelayUpload.js forwards agent-side PNG screenshots to per-client Discord channels. This is the first wave of the campaign to ship rotated AES key material (new DEPLOYMENT_KEY_A/KEY_B/MASK_A/MASK_B byte arrays, hex 12335cede9edad1edbce89fd3ef0836c8edd3778e48f3f38f2330198ec8b1eb0), verified byte-identical across the four donimique-account packages (zod-pino434, zod-pino444, zredis-typed, pinokio-redis) — a single shared build. C2 212.193.3.61 (AS206216, Advin Services LLC, Nurnberg DE) is reused from the Wave 3 pino-zod/zod-pino IP rotation. The campaign is definitively linked by shared C2 infrastructure, the hardcoded '.forge-jsxy' durable directory, the dist/deploymentCipherData.js + dist/deploymentDefaults.js XOR-key fingerprint, and the '# forge-jsx' README tell that spans multiple package names and npm accounts. Only one version of pinokio-redis (1.0.127) exists and all versions are malicious. Tarball SHA-256: a400b0342add77fd3a58e086334b35e11d79e234b180bb360f48adcd61ec4acd, SHA-1: 04b6035df92ef9eb790d64d425c05c51fce46ca7. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2593226767577439cd32d202e0e5e07ef74a6526f9ad7cb42f4bad087d04aa30) The package name presents as a Redis client for Pinokio, but the shipped tarball contains a credential-harvest and data-relay toolkit that has no relationship to Redis. dist/discordRelayUpload.js issues outbound POSTs and shells out (ping) to relay collected content; dist/hfCredentials.js and dist/secretScan/contentScanner.js decode base64-embedded blobs (Buffer.from(..., 'base64')) at runtime; dist/secretScan/agentStartupAudit.js performs fetch() calls to huggingface.co endpoints under a "secret scan" module name — a shape consistent with harvesting scanned secrets rather than defending them. dist/deploymentDefaults.js and scripts/encode-deployment.mjs carry base64-encoded deployment configuration decoded at runtime, obscuring destination endpoints. scripts/postinstall-agent.mjs runs at npm install (postinstall) and issues network activity (GET, ping) on install without user interaction, providing auto-execution on default install. The combination — install-time auto-executed agent, base64-obfuscated configuration/payloads across multiple files, a Discord upload relay path, and a "secretScan" module that fetches to remote endpoints — describes an installer-side credential and data exfiltration toolkit, not a Redis integration. Name/purpose mismatch, install-time execution, and multi-file obfuscation together satisfy the active-attack shape. ## Source: ghsa-malware (d8c9c7ad731c0929056de138dff2c461e808854d25aea316f6fe865a3d04d8c0) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full co | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database zredis-typed is a malicious npm package and part of the multi-wave "forge-jsx" cross-platform RAT campaign (Wave 4). It was published by npm account 'donimique' (donimiqueakers@gmail.com). The package.json description ('Node.js integration layer for Autodesk Forge') and the bundled README.md (literally titled "# forge-jsx") do not match the package name or the shipped code. On npm install the declared postinstall chain (postinstall-clipboard-event.mjs, ensure-dist.mjs, postinstall-durable-materialize.mjs, postinstall-bootstrap.mjs, postinstall-agent.mjs) runs scripts/postinstall-agent.mjs, which spawns dist/cli-agent.js as a detached, window-hidden background process. The agent connects over WebSocket to a command-and-control relay whose host, ports and default password are stored as an AES-256-GCM blob in dist/deploymentCipherData.js and decrypted at runtime by XOR-reconstructing a 32-byte key from two halves embedded in dist/deploymentDefaults.js. The decrypted C2 configuration is publicHost 212.193.3.61, relayPort 9877 (WebSocket relay), apiPort 8765 (HTTP API), default password 'secret'. Postinstall also registers OS-level autostart (Windows Run key, macOS LaunchAgent, Linux systemd/XDG autostart; service name forge-js-worker) pointing at a durable copy of the agent stored in a hidden '.forge-jsxy' directory under the platform application-data folder, so the implant survives removal of the npm package. Once running it performs credential-grade theft: dist/secretScan/agentStartupAudit.js walks the filesystem for BIP39-checksum-valid mnemonics, secp256k1/WIF private keys and BIP32 extended keys (xprv/tprv/zprv); dist/chromiumExtensionDbHarvest.js enumerates Chromium/Edge/Brave/Vivaldi/Yandex/Opera profiles across Windows, macOS and Linux and copies extension LevelDB stores (including MetaMask/Phantom-shaped wallet stores); harvested data is uploaded to the Hugging Face Hub using an embedded hf_ write token (dist/hfCredentials.js) or delivered via the relay; dist/hostInventorySend.js POSTs host inventory (hostname/platform/node/OS) to the relay and dist/discordRelayUpload.js forwards agent-side PNG screenshots to per-client Discord channels. This is the first wave of the campaign to ship rotated AES key material (new DEPLOYMENT_KEY_A/KEY_B/MASK_A/MASK_B byte arrays, hex 12335cede9edad1edbce89fd3ef0836c8edd3778e48f3f38f2330198ec8b1eb0), verified byte-identical across the four donimique-account packages (zod-pino434, zod-pino444, zredis-typed, pinokio-redis) — a single shared build. C2 212.193.3.61 (AS206216, Advin Services LLC, Nurnberg DE) is reused from the Wave 3 pino-zod/zod-pino IP rotation. The campaign is definitively linked by shared C2 infrastructure, the hardcoded '.forge-jsxy' durable directory, the dist/deploymentCipherData.js + dist/deploymentDefaults.js XOR-key fingerprint, and the '# forge-jsx' README tell that spans multiple package names and npm accounts. Only one version of zredis-typed (1.0.127) exists; all versions are malicious. Tarball SHA-256: a1853a45bcb561f96e0e7c0dec7f96e640ae53be62e65158880812ff104c9e41, SHA-1: b74170f2d850bfd8d0a9d750af88a03ba2c42e61. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (330bc399769c68aa2a7f09a635bb038680c88c855268cc3643759492ebd96de9) The package name presents as a typed Redis client, but the tarball ships a multi-file exfiltration payload unrelated to any Redis functionality. `dist/discordRelayUpload.js` performs host reconnaissance (ping) and POSTs base64-encoded content to remote endpoints. `dist/relayServer.js` similarly runs ping-based host probing. `dist/secretScan/agentStartupAudit.js` fetches attacker-controlled URLs on huggingface.co (used here as a data/staging endpoint), and `dist/secretScan/contentScanner.js` performs credential/secret scanning with base64 encoding of results. `dist/hfCredentials.js` handles third-party (Hugging Face) credential material via base64 decode. `dist/deploymentDefaults.js` and `scripts/encode-deployment.mjs` encode/decode deployment payloads via base64. `scripts/postinstall-agent.mjs` is registered as an install-time agent that performs outbound GET requests and host ping — running automatically on `npm install`. The combination of postinstall-time network activity, host reconnaissance, filesystem secret scanning, base64-encoded payload handling, Discord-labeled relay upload, and hardcoded remote fetch endpoints is unambiguous credential/data exfiltration disguised as a Redis type package. Nothing in the shipped modules implements a Redis client. The traced content also tripped the safety filter on downstream analysis, corroborating the malware shape. ## Source: ghsa-malware (73b8d51428450de7f67cb29aa402a94aefd62bdcf03e4f0eee43c554576eec2e) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (593662d3b4cda901642b713f419417807a33f3dca74e818f66e8d0cf9ebcf6e3) On `require('typedecode')` / `import 'typedecode'`, the bundled `dist/index.cjs` and `dist/index.js` execute an obfuscated import-time payload. A `bootstrap.js` IIFE exposes `require` and `module` on `global`, deobfuscates two large strings through a custom permutation (`YWG`), constructs a function via the `Function` constructor (`AQq(erE, YWG(fvm))`), invokes it on a second decoded payload to produce `XZs`, then calls `XZs(7942)` and brands `global._V = 'A6-Shadow-15'`. The deliberate placement of `require`/`module` on globals before the IIFE allows the decoded code to dynamically load arbitrary Node modules (fs, http, child_process, etc.) without any static reference. The package's API surface and inline comments are copied verbatim from the legitimate `decoders` package by nvie (including the email-regex comment and the pojo detection comment), and the README API (`object`, `array`, `optional`, `string`, `number`, `email`, `url`, `uuid`, `decode`/`verify`/`value`, `formatInline`, `formatShort`) duplicates that library — an impersonation lure to drive installs of the hidden loader. Author is the placeholder-style `chavanetsanastasia-netizen`. ## Source: ghsa-malware (bedd4815e96aa992468ab037dbd2c342b8567f07ece45674dd8a274c4e479912) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. | GCVE Database |
Page 1 of 2 · 1 duplicate CVE record merged