A new ClickFix campaign targets Windows users with a NodeJS-based infostealer delivered via malicious MSI installers. This highly adaptable remote access Trojan minimizes forensic footprints through dynamic capability loading, with core stealing modules and communication protocols delivered in-memory only after C2 connection. The malware routes gRPC streaming traffic over Tor network for persistent, masked bidirectional channels. An operational security failure exposed server-side admin panel protocol definitions, revealing a malware-as-a-service backend designed to manage multiple operators and automate cryptocurrency asset tracking. The modular architecture delivers malicious logic dynamically as strings executed in-memory, bypassing static signature detection while supporting full RAT functionality including shell command execution and wallet tracking.
The npm package 'localize-translate' version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, timestamp, and npm lifecycle event, then sends this data as JSON to a hardcoded third-party server without user consent. This behavior constitutes an undisclosed, unconditional reconnaissance callback rather than legitimate telemetry.
The npm package 'npm-wold' versions 1.1.1 and 1.1.2 contain malicious code that executes during installation. A postinstall script fetches JSON data from a remote attacker-controlled server and dynamically invokes a global function with attacker-supplied arguments, enabling arbitrary code execution on the installer's machine. This behavior is unexpected for the package's advertised functionality as an object-flatten utility.
The npm package gaarf-bq version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, and package metadata, then sends this data to a hardcoded external server without user consent. This behavior is unrelated to the package's documented functionality and resembles dependency confusion tactics. No official patch or remediation guidance is provided.
The npm package 'broadcast-graphics-mcp' version 1.0.0 contains malicious code in its postinstall script that automatically executes upon installation. This script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, npm lifecycle event, and timestamp, then sends this data as JSON to a hardcoded external server controlled by the package author. This behavior results in the exfiltration of installer machine metadata without user consent or configuration options.
The npm package 'tfjs-inference' version 1.0.0 is a typosquatting package targeting TensorFlow.js. It contains a postinstall script that automatically collects host identifiers such as hostname, platform, architecture, Node.js version, and package name, then sends this data as JSON to a hardcoded third-party server without user consent or notification. The package internally labels itself as a security research canary, but the data exfiltration destination is controlled by the author, raising significant privacy and security concerns.
The npm package core-js-gns version 1.0.0 contains malicious code executed during its postinstall hook. This code collects system information and sends it to an attacker-controlled server, then downloads and decrypts a payload which is executed on the installer's machine. The package impersonates the legitimate core-js library, enabling arbitrary remote code execution at install time.
The npm package 'lodahsjs' version 1.0.0 is a malicious typosquat of the legitimate 'lodash' package. It contains a postinstall script that performs hostile actions including sending system information to a hardcoded command-and-control server and downloading and executing a Windows binary from a suspicious GitHub release. The package has no legitimate functionality and is designed to deliver a malicious payload on Windows and Windows Subsystem for Linux (WSL) environments.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (152e5cdb52328dccd4eb61462c930b56f456dbdf759f0ce3005da3a7ecf4b688)
reqcrypt presents itself as a general-purpose HTTP client, but its internal PayloadProcessor unconditionally inspects every HTTP response for JSON keys named 'payloaddd', 'payload_gz', and 'payload_zlib', base64/gzip/zlib-decodes the associated values, and passes the decoded bytes to exec() inside the caller's Python process. This decode-and-exec path is wired into _process_response, which is invoked from every public verb (get/post/put/delete/patch/download/upload), so any server the caller contacts—or any network attacker able to tamper with a response—can push arbitrary Python code into the caller's process by adding one of those keys to a JSON body. In-source comments label the sinks as 'Hidden execution', and the behavior is not disclosed in the package's advertised API. Effect on any program using this library is a remote code execution channel driven by attacker-controlled or attacker-influenced HTTP responses.
## Source: kam193 (556f2178ed2505024fd91bc1c9c20b59d78783c27badd166a220493e5184fb39)
The package contains a hidden backdoor. The promised functionality is an HTTP request library with some additional functions. On every usage, code secretly checks for the presence of specific fields in the response, and if they are found, their content is secretly executed.
---
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-reqcrypt
Reasons (based on the campaign):
- backdoor
MobSF is a mobile application security testing tool used. Prior to 4.5.1, get_browsable_activities in mobsf/StaticAnalyzer/views/android/manifest_analysis.py validates only an Android manifest android:host value with valid_host before appending a separately supplied android:port to the URL fetched by _check_url, allowing an authenticated user to upload a crafted APK that makes requests to an attacker-selected nonstandard port at /.well-known/assetlinks.json. With an attacker-controlled hostname and DNS rebinding between validation and the requests.get connection, the request can reach an internal service, although redirects remain disabled and the path is fixed. This issue is fixed in version 4.5.1.
MagicMirror² is an open source modular smart mirror platform. Prior to 2.37.0, when hideConfigSecrets is enabled, the catch-all socket dispatcher in js/node_helper.js passes every inbound object payload through replaceSecretPlaceholder in js/server_functions.js before invoking socketNotificationReceived. A client connected to a loaded module namespace can submit a SECRET_API_KEY placeholder, causing the server to replace it with the corresponding process environment value. The default weather helper accepts INIT_WEATHER, copies the attacker-controlled instanceId, and returns it in WEATHER_ERROR, providing an echo path for the expanded secret. This reverses the intended one-way redaction boundary and can disclose API tokens, credentials, or service keys stored in SECRET_ variables. This issue is fixed in version 2.37.0.
MagicMirror² is an open source modular smart mirror platform. Prior to 2.37.0, MagicMirror applies ipWhitelist only as Express middleware, while the Socket.IO server in js/server.js is attached directly to the HTTP server without equivalent IP allowlist, origin, or namespace authentication checks. In a documented non-loopback deployment that relies on ipWhitelist, an unauthenticated adjacent-network client can connect directly to module Socket.IO namespaces, and js/node_helper.js dispatches arbitrary events and payloads to socketNotificationReceived. The default newsfeed and calendar helpers can make server-side requests to attacker-selected URLs, while the default updatenotification helper can reach child_process.exec when a third-party module update is pending and the attacker supplies an update command through the socket CONFIG path. This can expose internal services, manipulate module-helper state, and conditionally execute commands. This issue is fixed in version 2.37.0.
Adaguc-server is an open source geographical information system to visualize, combine, compare and share real-time meteorological, climatological and remote sensing data via OGC standards. Versions prior to 7.2.2 crash with a memory-safety fault when it parses a GeoJSON document whose geometry contains a malformed coordinate. The coordinate parser in `adagucserverEC/CConvertGeoJSON.cpp` indexes `pt.u.array.values[0]` and `pt.u.array.values[1]` and uses `polygon.u.array.length` as a loop bound without first validating the JSON node type or the coordinate length. A coordinate that is an empty array, a one-element array, a scalar, or `null` leads to an out-of-bounds heap read or a NULL pointer dereference. The same unchecked pattern is present in four geometry branches: `Polygon`, `LineString`, `MultiLineString` and `MultiPolygon`. The vulnerable parser runs whenever the server processes a local GeoJSON file, either a configured GeoJSON dataset or a GeoJSON file exposed through the `AutoResource` feature and requested by an unauthenticated WMS request. A crafted GeoJSON file reliably crashes the backend process that handles that request. Version 7.2.2 patches the vulnerability.
Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.5.3, seroval.fromJSON() allows attacker-controlled JSON Promise control nodes to operate on values from the general deserialization reference table without verifying genuine internal Promise resolver records, causing deserialization side effects with plugins enabled and potentially unintended server-side invocation or remote code execution when downstream frameworks register callable wrappers. This issue is fixed in version 1.5.3.
SWE-agent's trajectory inspector (sweagent inspector) version 1.1.0 includes an HTTP server that improperly handles path traversal sequences in its /trajectory/ handler. This flaw allows unauthenticated remote attackers to read JSON files outside the intended directory by exploiting parent-directory references ('..'). The server listens on all interfaces, applies wildcard CORS, and requires no authentication, increasing exposure. The disclosed files must be JSON shaped like trajectories, potentially leaking repository contents, command output, and secrets or API keys.
A security update for Node.js 24 on Red Hat Enterprise Linux 9 addresses multiple vulnerabilities including arbitrary code execution in SQLite FTS5, denial of service in brace-expansion, and server-side request forgery in ip-address parsing. These issues could allow attackers to execute code, cause crashes, or bypass trust boundaries. The update is rated as important by Red Hat Product Security and affects various architectures of Red Hat Enterprise Linux 9. Users are advised to apply the update as detailed in the Red Hat advisory.
Red Hat has issued a security update for nodejs22 on Red Hat Enterprise Linux 10 addressing multiple vulnerabilities. These include two denial of service (DoS) flaws in the brace-expansion package caused by memory exhaustion and unbounded intermediate arrays, and a server-side request forgery (SSRF) vulnerability in the ip-address package due to inconsistent IP address parsing. The update mitigates these issues to prevent potential service disruption and trust-boundary bypass.
CVE-2026-19978 is an OS command injection vulnerability in the jiantao88 android-mcp-server component. The flaw exists in the child_process.exec function within build/index.js, where manipulation of certain input arguments can lead to command injection on the local host. Exploit code has been published. The product uses a rolling release model, so specific affected or patched versions are not available. A patch identified by commit 14e2bf27c88ba137e35cbb0c2a75f72b595bb98a is recommended to fix the issue. The CVSS 4.0 base score is 4.8, indicating medium severity.
Token Optimizer MCP version prior to 5.1.0 contains an unauthenticated path traversal vulnerability in its dashboard session log API endpoints (/api/session-summary and /api/session-events). The endpoints accept a sessionId parameter that is directly concatenated into a filesystem path without proper sanitization, allowing attackers to read arbitrary .jsonl files on the server. This can expose sensitive session log data. The vulnerability has a CVSS score of 5.3 (medium severity) and is fixed in version 5.1.0.