Uncontrolled Resource Consumption vulnerability in Apache InLong. Users could affect operational configuration or allow upload of non-official packages.
This issue affects Apache InLong: from 2.0.0 before 2.4.0.
Users are advised to upgrade to Apache InLong's 2.4.0 or cherry-pick [1] to solve it.
[1]
https://github.com/apache/inlong/pull/12095 https://github.com/apache/inlong/pull/11732
Uncontrolled Resource Consumption vulnerability in Apache InLong. Non-template responsible persons can view template information.
This issue affects Apache InLong: from 2.0.0 before 2.4.0.
Users are advised to upgrade to Apache InLong's 2.4.0 or cherry-pick [1] to solve it.
[1]
https://github.com/apache/inlong/pull/12093 https://github.com/apache/inlong/pull/11732
Red Hat has issued a security update for osbuild-composer, a service used to build customized OS artifacts including VM images and OSTree commits. The update addresses two vulnerabilities: CVE-2026-39821, a privilege escalation issue due to incorrect Punycode label processing in golang.org/x/net/idna, and CVE-2026-55677, an unauthorized information disclosure caused by URL path decoding discrepancies in github.com/labstack/echo. These vulnerabilities affect Red Hat Enterprise Linux 9.6 Extended Update Support and related variants. The update is rated as Important by Red Hat Product Security.
A vulnerability was determined in GreyDGL PentestGPT up to 1.0.0. This vulnerability affects unknown code of the component Web-Page Crawling. Executing a manipulation of the argument Traceback can lead to injection. The attack can be executed remotely. A high complexity level is associated with this attack. It is stated that the exploitability is difficult. The exploit has been publicly disclosed and may be utilized. The reported GitHub issue was closed with the label "not planned".
CVE-2026-76761 is an OS command injection vulnerability in chenhg5 cc-connect versions 1.4.0 and 1.4.1. It affects the shellExecCommand function in the core/engine.go file of the Management API component. The vulnerability allows remote attackers to manipulate the exec argument to execute arbitrary OS commands. Exploit code is publicly available, but there is no indication of active exploitation in the wild. The issue was reported but the related GitHub issue was closed due to inactivity.
CVE-2026-76139 is a vulnerability in the acm-operator-bundle component of Red Hat Advanced Cluster Management for Kubernetes 2.11. The build process downloads and executes a script from a remote source without verifying its authenticity, allowing the script to access sensitive build credentials such as GitHub tokens and registry passwords. This could enable a remote attacker to inject malicious code and compromise the build environment and resulting operator bundle.
CVE-2026-63187 is a code injection vulnerability in logto-io's logto product affecting versions from 1.40.1 up to but not including 1.41.0. The issue arises from unsafe interpolation of the GitHub pull request title into a shell command within a GitHub Actions workflow, allowing an attacker to inject arbitrary shell commands. The vulnerability is mitigated by the use of a read-only GITHUB_TOKEN that does not expose repository secrets, limiting impact to disruption or alteration of the ephemeral workflow execution. This vulnerability is fixed in version 1.41.0.
The npm package 'comand' version 1.0.0 contains malicious code that executes automatically upon installation. Its postinstall script sends system platform information to a hardcoded IP address and downloads a potentially harmful executable from a GitHub repository. The executable is launched stealthily on Windows systems or via a PowerShell bridge from WSL. The package name appears to be a typosquat of 'command', and the binary is unsigned and unverified.
The sui-move-gql npm package version 1.0.2 contains malicious code that, upon import, reads sensitive files from the installer's home directory, including Sui wallet keystore and AWS credentials. It exfiltrates this data by encoding it and sending it to a GitHub repository controlled by the attacker. The exfiltration endpoint and authentication token are dynamically fetched and obfuscated to allow runtime rotation, complicating detection and mitigation. The malicious code targets developer workstations with live Sui wallet keys and avoids execution in CI environments. After exfiltration, it overwrites its own code to remove evidence, hindering forensic analysis.
The npm package commandor-cli version 1.0.0 contains malicious code in its postinstall script. This script XOR-decodes a hardcoded URL to download a binary from a personal GitHub repository, writes it to the temporary directory, and executes it detached. On Windows Subsystem for Linux (WSL), it uses a PowerShell command to execute the binary on the Windows host, extending the attack surface. Additionally, the script sends an install beacon with platform information to a hardcoded IP address over unencrypted HTTP. The binary is unsigned and fetched from an untrusted source, and the payload URLs and commands are obfuscated using XOR encoding.
The ladash-cli npm package is a malicious typosquat of lodash-cli that executes harmful code during installation. Its postinstall script downloads and runs a Windows executable from an unrelated GitHub repository, enabling full code execution on the host. It also detects Windows Subsystem for Linux (WSL) environments to execute a PowerShell bridge command, delivering the same payload. Additionally, it sends an unencrypted beacon to a suspicious IP address upon installation. The package version 1.0.0 is affected.
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.
The npm package 'testingsmthb1g' version 1.0.0 contains malicious post-installation code that downloads and executes a payload from a personal GitHub repository. The postinstall.js script uses XOR obfuscation to decode a URL and a PowerShell command, which it uses to fetch and run a Windows executable, including escaping from WSL/Linux environments to the Windows host. It also sends platform information to a hardcoded IP address. This behavior constitutes a malicious package with install-time code execution.
The typescriptt-core npm package is a typosquatting malicious package impersonating the TypeScript ecosystem. It contains no legitimate functionality but runs a post-install script that XOR-decodes a hidden URL and PowerShell command. On Windows, it downloads and executes a malicious executable from a GitHub release URL. On Windows Subsystem for Linux (WSL), it invokes PowerShell on the Windows host to perform the same action. Additionally, it sends a beacon with host platform information to a hardcoded IP address over unencrypted HTTP. The package affects version 1.0.0 and is designed to evade static analysis by obfuscating its payload and commands.
The npm package 'typescirpt-cli' version 1.0.0 contains malicious code in its postinstall script that downloads and executes an unverified executable from a personal GitHub repository. It uses obfuscated code to reconstruct the download URL and a PowerShell command to run the binary on Windows and Windows Subsystem for Linux (WSL) environments. Additionally, it sends installation metrics over unencrypted HTTP to a hardcoded IP address. The package name is a typosquat of the legitimate 'typescript-cli' package.
The npm package 'typecript-cli' version 1.0.0 is a typosquatting malicious package impersonating 'typescript'. Its postinstall script performs an install-time dropper attack by downloading and executing an unsigned executable from a personal GitHub repository. It uses obfuscation techniques such as XOR-decoding payload strings and assembling IP addresses from split arrays to evade detection. On Windows, it downloads and runs 'main.exe' without verification. Under Windows Subsystem for Linux (WSL), it escapes the Linux sandbox to execute the same payload via PowerShell. The script also sends a beacon with platform information to a hardcoded IP address, likely for command and control or host selection purposes.
The npm package 'tyepescript-cli' is a typosquatting malicious package impersonating the legitimate 'typescript' package. Its postinstall script uses XOR obfuscation to decode attacker-controlled URLs and commands. On Windows, it downloads and executes a malicious binary from a suspicious GitHub account. Under Windows Subsystem for Linux (WSL), it uses a PowerShell bridge to execute the same payload on the Windows host. The script also sends an install-time beacon to a hardcoded IP address. This behavior indicates an active attempt to compromise systems during package installation.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (004770b4da0c6705f95ef2c8654fd81d37650ffacaad7160041bded02cdb7fbc)
httpz-requests exposes a Telegram bot (`start_bot`, `run_cmd_enc`, `http_request`) whose message handler executes arbitrary shell commands on the host running the package, granting a remote Telegram operator full command execution under the installer's user account. Documented remote commands include arbitrary shell execution (`chalao`, `.sh <command>`, `.py <file>`, `.exec <file>`), destructive filesystem operations (`rm -rf <path>`), single- and bulk-file exfiltration (`take <file>`, `take all`), a full-host backup mode that produces split 50MB archives with `.partNNN` chunking (`get all`), and environment-variable dumping (`.printenv`) — collectively enabling remote theft of filesystem contents and process-environment secrets (cloud, CI, and API credentials). The package is shipped only as compiled Cython `.so` files with no Python source, and self-describes obfuscation features that XOR+base64-encode command strings and disguise execution as `http_request("POST",...)` so plaintext commands do not appear in `ps` or system logs; the Telegram bot token is stored encoded and decoded at runtime by `dec()`. The distribution name `httpz-requests` and import name `httpz_requests` resemble the top-100 PyPI package `requests` while presenting a Telegram remote-shell API instead of an HTTP client, and metadata is unfilled boilerplate (author `Aapka Naam <you@example.com>`, homepage `https://github.com/YOUR_GITHUB_USERNAME/httpz-requests`).
## Source: kam193 (38eff923106836997e28de6d7173a1553da126be230b341fe64f0c4c215769a2)
The package provides Telegram-based remote access to the machine it runs on. It was deliberately created and used to hack other machines, exfiltrate files and credentials. This package automatically ensures persistence and starts a malicious process on import.
---
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-httpz-requests
Reasons (based on the campaign):
- files-exfiltration
- rat
- persistence
- uses-telegram-bot
- obfuscation
- native-extension