---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (08547edeec8e522d84b40fd8236878da54c888ede86588be3913a1c37cd2b245)
infogram-bot@1.6.0 implements a Telegram bot that accepts text messages from remote parties and passes them directly to subprocess.check_output(cmd, shell=True,...) on the host running the package, giving any authorized Telegram user (and, for the.sh command, any member of a group chat) arbitrary shell command execution with the privileges of the process. Additional handlers expose 'get all' (walks the working directory, zips it, and uploads all files in 50MB chunks via reply_document), 'take <file>' / 'tk a' (streams any requested file or all files under the cwd back to the Telegram chat), '.printenv' (iterates os.environ and sends every environment variable value to the chat), and '.grep' (greps environment values and files for arbitrary substrings and returns matches). Together these provide a full remote-shell backdoor plus a data-exfiltration channel to a destination the host owner did not configure at runtime. pyproject.toml also ships placeholder maintainer metadata (author 'Aapka Naam' / you@example.com, Homepage containing the literal 'YOUR_GITHUB_USERNAME'), consistent with low-attribution publication.
## Source: kam193 (454fa32963f58275e35167d59dd581240725e099682e76e44b6fca7b22332cb0)
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.
---
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
RAGFlow before 0.26.3 contains a server-side request forgery vulnerability in the agent workflow "Invoke" component (agent/component/invoke.py). The component builds an outbound request URL from canvas configuration and runtime template variables and passes it to requests.get, requests.post, or requests.put without calling the shared assert_url_is_safe validator or pinning the resolved address, unlike the crawler, SearXNG, file-upload, and RSS fetch paths. A user who can create or trigger an agent can direct the server to fetch loopback, link-local, and RFC 1918 destinations, including cloud instance metadata endpoints and services co-located on the deployment network, and the response body is returned as the component output. Where an agent is configured to interpolate the chat query into the Invoke URL, the destination is chosen by whoever can send that query.
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.3.24 contain an incomplete fix for CVE-2026-27486. The `!stop` chat command uses an unpatched function that immediately sends SIGKILL to background bash processes without first sending SIGTERM, preventing graceful shutdown. This behavior was intended to be fixed by introducing a graceful shutdown sequence that sends SIGTERM first and only escalates to SIGKILL after a grace period. The incomplete fix leaves a copy of the vulnerable kill function in the codebase, which is still used by the `!stop` command. A patch is available in OpenClaw 2026.3.24 that addresses this issue.
A vulnerability in the openclaw-cli package allows a gateway operator with write permissions to reach admin-class Talk Voice configuration persistence via the chat.send function. This issue affects versions from 2026.1.29 up to but not including 2026.3.28. The vulnerability is considered medium severity and has been fixed in version 2026.3.28.
OpenClaw CLI versions up to 2026.2.17 have a vulnerability where the ACP prompt-size checks are missing in the local stdio bridge. This allows very large prompt text blocks to be accepted and assembled into oversized payloads before being forwarded to chat.send. The issue mainly affects local ACP clients, such as IDE integrations, that send unusually large inputs. The vulnerability can reduce responsiveness in local ACP sessions and increase model usage and costs. There is no privilege escalation or direct remote attack vector in the default ACP model. A patch is planned for version 2026.2.18.
OpenClaw CLI versions prior to 2026.2.2 have an authorization bypass vulnerability where clients with only 'operator.write' permissions can approve or deny exec requests by sending the '/approve' chat command. This bypasses intended permission scoping, allowing unauthorized approval actions. The issue mainly affects multi-client setups with scoped tokens. A fix is available in version 2026.2.2 that enforces proper permission checks for the '/approve' command.
OpenClaw CLI versions 2026.2.22 and 2026.2.23 contain an authorization flaw in the synology-chat channel plugin. When the dmPolicy is set to allowlist but the allowedUserIds list is empty or unset, unauthorized Synology senders can dispatch agents. This issue requires specific plugin setup and sender access, leading to a medium severity classification. The vulnerability is fixed in version 2026.2.24.
OpenClaw CLI versions up to 2026.3.1 have a vulnerability in webhook handlers for BlueBubbles and Google Chat where request bodies are parsed before authentication. This allows unauthenticated attackers to send slow or oversized request bodies, causing a denial of service by tying up parser resources. The issue is fixed in version 2026.3.2 by enforcing authentication before body parsing and adding strict limits on request processing time and size.
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.4 contain a vulnerability where authorized non-owner chat senders can issue device-pairing bootstrap codes via the /pair command. This allows them to enroll devices with operator/node capabilities, which retain persistent credentials until removed. The vulnerability requires the attacker to already have permission to send commands through a configured chat channel and does not affect unauthenticated users. The issue is fixed in version 2026.5.4.
OpenClaw CLI versions up to 2026.3.24 contain a vulnerability where sender policy resolution incorrectly downgrades a route-level group allowlist policy to open, allowing unintended interaction with bots. This affects Google Chat spaces and Zalouser groups, permitting any member of an allowlisted group to interact with the bot despite intended sender-level restrictions. The issue is fixed in version 2026.3.28.
CVE-2026-35621 is a privilege escalation vulnerability in openclaw-cli versions >=2026.1.29 and <2026.3.24. It allows a gateway client with operator.write scope to persistently modify channel authorization allowlists, a capability intended only for operator.admin scope. This occurs because the /allowlist command does not enforce the required admin-level privilege before writing configuration changes, unlike other config mutation commands. The issue is fixed in version 2026.3.24.
A vulnerability in openclaw-cli allows scoped Gateway clients with operator.write scope to bypass admin command scope gates via inherited external chat.send routes. This enables execution of commands requiring higher privileges such as operator.approvals or operator.admin. The issue affects versions from 2026.1.29 up to but not including 2026.5.18. A patch is available in version 2026.5.18. Until upgraded, avoid granting operator.write tokens to clients that can deliver commands into sessions with external routes unless fully trusted.
OpenClaw CLI had a vulnerability in its chat.send gateway where ACP-only provenance fields were controlled by self-declared client metadata from the WebSocket handshake instead of verified authorization. This allowed authenticated operator clients to spoof ACP identity labels and inject reserved provenance fields meant only for the ACP bridge. The issue was fixed in version 2026.3.28.
A vulnerability in openclaw-cli allows write-scoped authorized users to persist verbose output session overrides via the chat.send path, which should be restricted to admin-only access through sessions.patch. This could lead to unintended exposure of verbose output or tool reasoning beyond intended operator limits. The issue affects versions from 2026.1.29 up to but not including 2026.3.28. The vulnerability is fixed in version 2026.3.28.
OpenClaw CLI versions prior to 2026.4.2 have a vulnerability in the Zalo webhook replay deduplication mechanism. The dedupe keys were not sufficiently scoped across chat and sender dimensions, causing legitimate events from different conversations or senders to be incorrectly identified as duplicates and dropped. This results in silent message suppression and can disrupt bot workflows by causing availability issues in webhook event processing. The issue is fixed in version 2026.4.2.
A vulnerability in Openclaw CLI's OpenClaw Gateway allows a user with write permissions to reset sessions via the chat.send command, which should be restricted to admin-only operations. This flaw enables unauthorized session rotation and transcript archiving without admin privileges. The issue affects versions from 2026.1.29 up to but not including 2026.3.28. The vulnerability has been fixed in version 2026.3.28.
The Openclaw CLI's Google Chat integration allows authorization based on mutable email principals in its allowlist, weakening identity binding. This can lead to spoofing access if an attacker has Google Workspace or IdP administrative control to reassign email addresses. The issue is low severity because requests are authenticated via Google Chat tokens, and exploitation requires high privilege access. The vulnerability affects openclaw versions from 2026.1.29 up to but not including 2026.2.14. A patch is available that deprecates treating 'users/<email>' as an email allowlist entry and recommends using immutable user IDs instead.
A vulnerability in the openclaw CLI allows a gateway client with operator.write privileges to perform persistent configuration changes via the chat.send command interface, which was intended to be restricted to operator.admin users. This issue arises from an authorization mismatch in the handling of /config set and /config unset commands routed through chat.send. The vulnerability was patched in version 2026.3.7. Exploitation requires an authenticated gateway client with specific permissions and enabled command support. The severity is rated medium due to the scoped nature of the privilege escalation and the requirement for prior authentication.
WhatsApp has introduced an optional 'Scam Alert' feature that uses an on-device machine learning model to warn users about potential scam messages. The feature analyzes incoming messages from non-contacts for scam patterns without sending message content off the device, preserving user privacy and end-to-end encryption. Users receive warnings when a message is suspected to be a scam and can choose to block, report, or trust the chat. The feature is currently in a limited beta rollout and can be disabled by users at any time. This initiative complements previous WhatsApp security enhancements aimed at protecting users from fraud and spyware attacks.
Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, and 8.6.1, the stream-notify-user stream in the WebSocket protocol allows an authenticated user to write arbitrary notification bodies because the sender is not checked, and the client-side UI can create an ephemeral fake message in another user's currently open chat. This issue is fixed in versions 7.10.14, 8.0.8, 8.1.7, 8.2.7, 8.3.7, 8.4.5, 8.5.2, and 8.6.1.