JSCeal is a sophisticated cryptocurrency-focused stealer malware delivered as compiled V8 bytecode executed by a bundled Node.js runtime. It employs multiple layers of JavaScript obfuscation and encryption, including RC4 and AES-256-CBC, to protect its payload. The malware's capabilities include keylogging, browser credential theft, cryptocurrency collection, HTTPS traffic interception via a local man-in-the-middle proxy, and session replay using stolen cookies. Recent variants target macOS and newer V8 versions, showing active development. Check Point Research developed a fully static deobfuscation pipeline to analyze JSCeal without executing it, enabling detailed understanding of its behavior. The toolkit is publicly available and supports analysis of multiple samples.
This Red Hat security advisory addresses multiple vulnerabilities in Node.js 24, including unauthorized filesystem access due to a permission model enforcement flaw, remote memory exhaustion via HTTP/2 retained header blocks, and a heap-use-after-free vulnerability in HTTP/2 handling that can lead to denial of service. The update rebases Node.js 24 to the latest release to include these security fixes along with bug fixes and enhancements. The advisory rates the security impact as Important and provides updated packages for Red Hat Enterprise Linux 10 across various architectures.
Nodemailer versions before 6.9.9 contain a regular expression denial of service (ReDoS) vulnerability in the email parsing functionality when the attachDataUrls parameter is enabled or when processing embedded file attachments. This vulnerability allows attackers to send specially crafted emails with malicious data URLs or embedded attachments that can cause the Node.js event loop to hang, resulting in a denial of service condition. The vulnerability does not impact confidentiality or integrity but affects availability.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (d10f01e2954dde5faac23074d02bb989f22d0dcb78be82c1c4417531fef8b859)
The package ships a bundled Node script pyservercheck/js/main.js whose visible top half is a healthcheck stub matching the README, followed by a long run of tab whitespace and a trailing eval(atob('...')) that decodes to a two-stage loader. The decoded loader queries public Ethereum RPC endpoints (eth.blockscout.com, 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) for the latest transaction from the hardcoded sender 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, extracts an IPv4 pair from the tx `to` field, fetches XOR-obfuscated stage-2 code from http://<decoded-ip>:443/0x/cls and /0x/ls, eval()s it, and re-launches it via a detached `spawn('node', ['-e', <code>])`. Execution is wired to two auto-triggers: pyproject.toml overrides setuptools `build_py` and `develop` with pyservercheck._setup_cmd.BuildPy/Develop, whose `run()` calls _run_main_js_now() -> subprocess.run(['node', main.js]) during `pip install` / `pip install -e.`; and BuildPy also writes a `pyservercheck.pth` file containing `import pyservercheck._hooks; pyservercheck._hooks.ensure_once()`, which Python auto-executes at every interpreter startup, invoking run_js() again. The `.main_js_ran` marker is advisory and can be removed to force re-execution. The C2 destination is rotatable by publishing a new Ethereum transaction from the sender address, so the fetched payload is fully attacker-controlled at each run.
## Source: kam193 (4b365b9df06973db4f112bdbf2ad704dcc91c1b7b3eaceddb06a8e884c3f760a)
Package embeds obfuscated, JS-based malware downloading further remote stages. The code is triggered during building the package and on every Python startup (via PTH file). The next-stage IP is delivered via a blockchain.
The payload and embedded IoCs are consistent with campaigns attributed to Lazarus APT/PolinRider.
---
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-pybitjs
Reasons (based on the campaign):
- obfuscation
- Downloads and executes a remote malicious script.
- malware
- abuses-pth
- c2-in-blockchain
A vulnerability in the ljharb qs library causes qs.stringify to throw a TypeError when serializing objects whose own constructor property has a truthy but non-callable isBuffer member. This occurs because the isBuffer check calls obj.constructor.isBuffer without verifying it is a function. The issue affects versions from 2.2.5 up to but not including 6.16.0 and was fixed in version 6.16.0. An attacker can craft input that triggers this error, causing synchronous exceptions during serialization. In typical Node.js HTTP frameworks, this results in a 500 error response without crashing the process, but in some cases, such as async handlers or background jobs without error boundaries, it can cause process termination.
A security update for Red Hat Hardened Images RPMs addresses multiple vulnerabilities in the grafana13.2 package, including CVE-2026-75899, which involves a flaw in the fast-uri Node.js library. This flaw allows double decoding of percent escapes in hostnames, enabling Server-Side Request Forgery (SSRF) and bypass of host-based security policies. The update includes fixed RPMs for aarch64 and x86_64 architectures. No explicit patch details are provided, and mitigation options are limited or unavailable according to Red Hat.
The npm package @testrelic/playwright-analytics version 2.13.0 contains malicious code embedded in its postinstall script. This script uses obfuscation techniques including whitespace padding and a custom shuffle to hide a payload that dynamically executes arbitrary code. The payload gains access to Node.js built-ins by assigning key globals to the global object, enabling potentially harmful operations. Additional bundled files in the package invoke child processes and make outbound HTTP POST requests, inconsistent with the package's declared purpose as a Playwright analytics reporter.
The npm package supersignaturenature versions 1.0.5 and 1.0.6 contain malicious code in their published distribution bundles that is not present in the source tree. This code decrypts an encrypted token using a DES key imported from a dependency that can be updated independently, then executes the decrypted JavaScript via a spawned Node.js process. This behavior effectively allows arbitrary code execution controlled by the dependency manager-thedate. Any system with this package installed should be considered fully compromised, and all secrets should be rotated from a different machine.
The npm package 'js-tokens-array' contains malicious code that executes arbitrary JavaScript during module load. It reconstructs a URL from a numeric char-code array to fetch JSON data from a remote host, then passes the 'token' field from this JSON to eval(), enabling remote code execution in the installer's Node.js process. The package name is a typosquat of the legitimate 'js-tokens' library, designed to lure users into installing it.
The js-array-tokens npm package version 1.0.2 contains malicious code that, upon module load, reconstructs a URL from an obfuscated character code array and fetches a JSON response from that URL. The package then passes the 'token' field from the response directly to eval(), executing arbitrary code within the Node.js process. This remote-loader pattern is concealed by obfuscation and has no legitimate use.
MariaDB Connector/Node.js versions prior to 3.2.4, 3.3.3, 3.4.6, and 3.5.3 contain a SQL injection vulnerability when using certain client character sets (big5, gbk, sjis, cp932, or gb18030). This occurs due to improper escaping of attacker-controlled Buffer parameters client-side, allowing an attacker to inject arbitrary SQL. The default utf8mb4 character set and prepared-statement execution paths are not affected. The vulnerability can lead to exposure or modification of data accessible to the database account. Fixed versions are available.
MariaDB Connector/Node.js versions prior to 3.2.4, 3.3.3, 3.4.6, and 3.5.3 can expose account passwords in cleartext during PAM dialog authentication over insecure transport. This occurs because the connector does not enforce secure transport for the PAM password authentication dialog, allowing a hostile or on-path server to trigger password disclosure over plain TCP. The issue is mitigated by using properly verified TLS or local Unix sockets. The vulnerability has a CVSS score of 5.9 (medium severity) and is fixed in the specified versions.
MariaDB Connector/Node.js versions prior to 3.3.3, 3.4.6, and 3.5.3 have an improper certificate validation vulnerability. When SSL is enabled without a pinned CA or server certificate, the connector may send credentials before completing certificate fingerprint validation. This allows a man-in-the-middle attacker to present a self-signed certificate, capture the database password, and authenticate directly even though the connection is later closed. The issue is fixed in versions 3.3.3, 3.4.6, and 3.5.3.
CVE-2026-82256 is a vulnerability in SvelteKit versions before 2.69.1 where the application fails to properly validate the size of remote form function payloads. This flaw allows attackers to send excessively large payloads that crash the Node.js process running the application. Repeated exploitation can cause a denial of service by continuously crashing the application process.
In July 2026, Microsoft Threat Intelligence uncovered a supply chain attack targeting the official AsyncAPI NPM organization. Attackers published malicious versions of multiple packages under the trusted AsyncAPI namespace, exploiting developer dependencies to distribute malware. The compromised packages deployed a multi-stage Remote Access Trojan through obfuscated lifecycle hooks that executed during routine build workflows. Upon installation, the malware retrieved second-stage payloads from IPFS gateways, established persistence on infected systems, and initiated command-and-control communications with external infrastructure. The attack leveraged trusted build automation and dynamic package retrieval via npx to bypass traditional security controls, affecting developers executing version-pinned tasks in their CI/CD pipelines.
CVE-2026-54732 is a path traversal vulnerability in the Node.js module libreoffice-convert prior to version 1.8.2. The module improperly handles the caller-controlled fileName parameter by using it directly in path.join without normalizing it to a base name. This allows an attacker to escape the intended temporary directory and write files to arbitrary locations writable by the process, potentially overwriting sensitive files such as SSH authorized_keys, cron configurations, or web root files. The issue is fixed in version 1.8.2.
Trilium is an open-source hierarchical note-taking application. In versions prior to 0.104.0, the default-on "Safe import" filter fails to neutralize the shareTemplate relation because that relation is not marked as dangerous, allowing an attacker-supplied import archive to plant a server-side template that leads to remote code execution. The relation is omitted from the built-in list of dangerous attributes, so unlike other code-loading relations it is not disabled on import, and when the victim later publishes the imported note the public share renderer feeds the linked EJS code note's raw bytes into ejs.render, which compiles them in the server's Node process. An unauthenticated request to the shared note then executes the attacker's JavaScript with full access to require, process, the filesystem, and the network. This issue is fixed in version 0.104.0.
A vulnerability in the node-modules urllib HTTP client for Node.js allows sensitive authorization headers and tokens to be sent to attacker-controlled redirected origins due to improper reuse of request options across different origins during redirects. This can expose credentials such as Authorization, Cookie, Proxy-Authorization, and various API tokens without user interaction. The issue affects versions prior to 2.44.1 and 4.9.1 and has a high severity rating.
The mham-js npm package version 1.0.4 contains malicious code that executes arbitrary attacker-controlled code upon import. It reads and decrypts an external encrypted payload using a hardcoded DES key, then runs this payload in a detached Node.js subprocess. The package's README falsely claims no action occurs on import, masking the malicious behavior.