Search: interactive-server.ts
49 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| –Not rated | – | AlienVault OTX General Mantax Otax is an Android malware targeting devices running Android 9 and earlier. It combines ransomware and spyware capabilities, encrypting files with AES and appending .enc extensions. The malware requests extensive permissions, including device administrator and accessibility access, to steal sensitive data such as screen recordings, browser history, PINs, contacts, call logs, SMS, and chats from WhatsApp and Telegram. It communicates with command and control servers via HTTPS and WebSockets, using dynamic domain resolution through GitHub. Version 2 introduces advanced features like UI hijacking, screen blocking, touch input interception, harassment capabilities, and remote text-to-speech. Data exfiltration is facilitated through Firebase and Catbox services, enabling a double-extortion scheme with an interactive ransom chat portal. | AlienVault OTX General | |||
| Critical | 9.3 | EPSS 1.1% | CVE-2026-86121trycua cua-computer-server · Missing Authentication Critical9.3EPSS 1.1%CVE Database V5CVE-2026-86121 Cua computer-server versions before 0.3.42 skip authentication when the CONTAINER_NAME environment variable is unset and bind to all interfaces by default, allowing unauthenticated attackers to execute arbitrary commands. Attackers can reach TCP port 8000 to run shell commands via the run_command endpoint, read and write arbitrary files through file operation endpoints, and access interactive PTY shells without authentication. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database The npm package '1nestjs' version 0.0.1 is a typosquatting malicious package that executes code during installation to exfiltrate environment variables and provide a remote shell to an attacker. It collects environment variables with keys matching sensitive patterns and sends them to a remote server, then opens an interactive shell connection to that server. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package '0nestjs' version 0.0.1 is a malicious typosquatting package targeting developers who mistype 'nestjs'. Upon installation, it executes a postinstall script that harvests environment variables containing secrets and sends them to a remote attacker-controlled server. It also establishes a reverse shell connection to the attacker, allowing interactive command execution on the victim's machine. | GCVE Database | |||
| –Not rated | – | Reddit NetSec This report discusses a novel approach to preventing prompt injection attacks in AI agent communication by enforcing containment as a structural property rather than relying on detection. The approach involves wrapping all incoming commands from peer agents as quoted data that cannot be interpreted as executable commands, effectively preventing unauthorized actions even if malicious input is accepted. The implementation is a 33 KB JavaScript module running entirely client-side without any language model or server interaction. It uses cryptographic signature verification and deterministic checks to block forged or replayed messages, unapproved agents, and unauthorized tokens. This containment layer ensures that even if an attack payload is delivered normally, it cannot be executed, eliminating the need for detection-based defenses. The solution is demonstrated interactively in a browser environment and is not a vulnerability or exploit but a security design concept. | Reddit NetSec | |||
| Malicious | – | MaliciousGCVE Database The npm package datetime-fmt-xutil version 1.0.0 contains malicious code in its postinstall.js script. This script opens a TCP connection to a hardcoded IP address and pipes a shell to the remote endpoint, granting interactive shell access to an attacker. The malicious behavior executes unconditionally during npm install and uses fallback methods with bash and python3 to establish the reverse shell. Failures are reported via HTTP GET requests to the attacker's server. The package's legitimate date-formatting functionality is a cover for this reverse-shell payload. | GCVE Database | |||
| –Not rated | – | Cisco Talos Cisco Talos recently identified an undocumented phishing framework, internally branded "JWR" by its developer, built to convincingly impersonate checkout and login pages across major payment and shopping platforms. The client engine of the JWR phishing framework is a real-time, operator-driven system that, rather than merely logging form submissions like a static credential-stealing page, keeps an AES-CTR encrypted WebSocket open to the threat actor so they can steer each victim's session live. The victim data targeted by the actor using JWR extends well beyond payment data, encompassing identity documents, Social Security numbers, passport and driver's license images, website and PayPal credentials, 2FA codes, and full device fingerprints, all committed to the actor's server once a session ends. Talos assesses with medium confidence that the JWR phishing framework is a variant of "The Outsider," a phishing-as-a-service (PhaaS) platform, based on several similarities in the client engine scripts and functionalities of the two PhaaS platforms. Talos observed a real-world campaign delivering the JWR client via SMS lures impersonating toll authorities, and postal and courier services of several countries in Southeast Asia and the Middle East. JWR phishing framework, a likely variant of the Outsider JWR is a phishing framework capable of harvesting complete payment card data, login credentials, and personally identifiable information (PII) documents and images in real time. The client-side engine of the framework impersonates login, and checkout flows of several payment gateways, including Shopify, PayPal, Apple, Klarna, and banks, while allowing the operator to stealthily control the victim session through an AES-CTR encrypted WebSocket channel. The client engine architecture is divided into a Host Bridge module that relays commands into a phishing inline frame (iframe) and a Vue.js victim application that renders across 44 phishing pages, streams the victim's keystrokes to the actor as they are typed, and carries out more than 40 distinct instructions issued from the command-and-control (C2) console. The data exfiltration schema is a cvvform object that includes fields such as credit card number, CVV, PIN, expiry date, Social Security Number (SSN), passport or ID images, two-factor authentication (2FA) codes, website logins, PayPal credentials, and device fingerprint. Talos discovered that the JWR client engine shares significant code and functional similarities with the client of The Outsider PhaaS platform operated by the Chinese-speaking actor “Outsider Enterprise,” which was reported by external researchers . JWR client architecture and workflow Figure 1. JWR phishing framework’s client engine architecture and execution flow. The execution starts when the parent phishing webpage loads and executes the client's engine. It checks a single global flag, window.__HOST_MODE , which is set by the parent phishing page, and selects one of two execution modes. If the flag is set, the script enters Host Mode, and control passes to the Host Bridge module, an immediately invoked function expression (IIFE) that operates within the parent page, typically a replica of a legitimate checkout or account login page, relaying received details into a child iframe that contains the actual phishing form. It establishes a persistent WebSocket connection to the actor’s C2 server. If the flag is not set, the page enters Content Mode, and control passes to the Vue.js Application, an interactive front end that renders the phishing pages, collects victim input, manages the flow across 44 HTML files, and handles the actor’s instructions from the C2 server, ultimately redirecting to a custom error page after sending the data to the C2. The Content Mode of execution has three communication modes: standalone, pluginIframe, and hostIframe. In standalone mode, the application fully owns its WebSocket connection. In pluginIframe mode, it has no direct link to t… | Cisco Talos | |||
| Malicious | – | MaliciousGCVE Database The internallib_v164 npm package contains malicious code that executes a reverse shell command upon invocation. This command fetches and runs a script from a remote server, opening an interactive shell to a hardcoded internal network address. This behavior grants an attacker arbitrary code execution and persistent access on the host machine. The affected package versions include 6.0.9, 4.0.9, 1.0.7, and 1.0.9. Removal of the package alone may not fully remediate the compromise, as the attacker may have already established persistent control. Immediate secret and key rotation from a different, uncompromised system is strongly advised. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The safe-local-env-loader npm package impersonates the legitimate dotenv package but contains malicious code that captures desktop screenshots every 3 seconds on Windows and macOS. It exfiltrates these screenshots along with system metadata to a hardcoded command-and-control server. Additionally, it polls the server for remote mouse and keyboard input commands, enabling interactive control of the infected host. On Windows, it establishes persistence by creating a startup script and registry entry to run the malicious agent on every user logon. Any software installing this package is exposed to screen-content theft, remote input injection, and persistent compromise. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The elephant-tusk-runner npm package versions 1.0.0 and 1.0.1 contain malicious code that starts an Express and WebSocket server bound to all network interfaces with open CORS and no authentication. This server exposes endpoints that allow remote attackers to spawn interactive shells and execute arbitrary commands on the host machine. The exposed functionality includes spawning bash or PowerShell shells, executing commands like git clone, npm install, PHP artisan commands, and killing arbitrary processes. This creates a severe remote code execution and remote shell access risk on any machine running the tool, especially on shared or reachable networks. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database The npm package @bananacool467/ui-tools, marketed as a UI-components library, contains malicious code that implements an unauthenticated WebSocket server exposing an interactive shell on the server. This backdoor allows remote command execution as the server process without any authentication or origin checks. The package ships both the server-side middleware and a browser client that together create a remote shell channel, posing a severe security risk to any system using it. | GCVE Database | |||
| Critical | 9.3 | EPSS 0.8% | CVE-2026-66747Zbtlink CPE2801 Firmware · Embedded Malicious Code Critical9.3EPSS 0.8%CVE Database V5CVE-2026-66747 Zbtlink router firmware ships an embedded remote-control implant, ENDLESSDOORS, present in every published build across the product line. It is the open-source ycsunjane/rctl tool built in as an OpenWrt package (librctl.so), started at boot and run as root under the process name kworker to blend in with the kernel's [kworker/*] threads. It opens no listening port; it phones home over cleartext TCP to a hardcoded command-and-control server (command channel 7000, interactive-shell callback 7001) with no authentication and no transport encryption, re-attempting contact roughly every 35 seconds. Its command handler passes any received string to popen() as uid=0, and a reserved rctlbash command returns an interactive root shell. Because the channel is unauthenticated and cleartext, control is not limited to whoever planted it: any party that answers at the C2 address, occupies the network path (DNS or route hijack), or acquires the hardcoded fallback domain obtains unauthenticated remote code execution as root. | CVE Database V5 | ||
| Medium | 5.4 | EPSS 0.4% | CVE-2026-17350pgAdmin 4 · Missing Authorization Medium5.4EPSS 0.4%CVE Database V5CVE-2026-17350 The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO handler in that tool's workflow relied solely on pga_login_required/socket_login_required, which check authentication but not the tool permission. The reporter verified three cases against a test build: (1) a user without tools_query_tool permission received 403 on the protected sqleditor initialization route, but the same session went on to connect the server, initialize the viewdata backend chain, and retrieve real table row content; (2) a user without tools_grant_wizard received 403 on the protected acl route, but the same session still enumerated grantable objects, generated GRANT SQL, and successfully applied it -- confirmed database-side via has_table_privilege(); (3) a user without tools_schema_diff received 403 on the protected panel route, but the same session initialized schema diff, enumerated and connected databases, and obtained real DDL differences via the compare_database Socket.IO handler. The reporter also confirmed a related but distinct issue: a non-owner triggering /misc/workspace/adhoc_connect_server against an administrator-owned shared server caused pgAdmin to persist a new server row still owned by the administrator (user_id/shared unchanged from the source), even though the connection attempt itself reported failure. During remediation, the same front-door-only permission gap was found to also affect the ERD, PSQL, and Debugger tools, and the Backup, Restore, Maintenance, and Import/Export blueprints, none of which were part of the original report; these were fixed using the same pattern as an extension of the reported defect class. An authenticated user who had valid pgAdmin login and a stored, working database connection, but had been explicitly denied a specific tool's permission by an administrator, could therefore still drive that tool end-to-end through its other routes and sockets, including obtaining an interactive psql session over the /pty Socket.IO namespace and invoking backup/restore/maintenance/import-export jobs. Because the bypass only restores access to tools operating over the user's own already-authenticated database connection, it does not grant the user any database privilege they did not already hold; it circumvents pgAdmin's own tool-level access-control policy (an organisational segregation-of-duties control, separate from database-level authorization), letting a user reach a pgAdmin feature an administrator intended to withhold from them, using capabilities their existing database role already permits through other means. Socket.IO event handlers had no permission-aware equivalent of permissions_required; only socket_login_required existed, checking authentication but not the tool permission. Fix adds a socket_permissions_required decorator (mirroring permissions_required, honouring the Administrator bypass, reading permissions via has_permission()) and applies it, alongside permissions_required, as the outermost decorator on every backend route and Socket.IO handler for the affected tools. Regression tests assert 403 on every gated route and socket handler for a permission-less user. This issue affects pgAdmin 4 in SERVER mode: from 9.3 before 9.17. | CVE Database V5 | ||
| High | 8.7 | EPSS 0.5% | CVE-2026-55768allinurl goaccess · Excessive Memory Allocation High8.7EPSS 0.5%CVE Database V5CVE-2026-55768 GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through the browser. Prior to version 1.11, the built-in WebSocket server narrows a 64-bit extended frame length into the signed 32-bit WSFrame.payloadlen field before enforcing the maximum frame size, allowing an unauthenticated remote client to bypass the guard and force an approximately 18-exabyte allocation request that terminates the process. This issue is fixed in version 1.11. | CVE Database V5 | ||
| Medium | 5.5 | EPSS 0.2% | Medium5.5EPSS 0.2%CVE Database V5CVE-2026-17534 Kimi Code (@moonshot-ai/kimi-code) before 0.27.0 implements FetchURL SSRF hardening as a static hostname and IP-literal denylist in assertSafeFetchTarget, without resolving DNS or re-validating hosts after HTTP redirects. An attacker who can influence a FetchURL call (for example via prompt injection) can supply a crafted public hostname that resolves to loopback or another internal address, or a public URL that redirects to such a target, and thereby reach internal network services that the denylist was intended to block. FetchURL is included in the default auto-approve tool set, so the call does not require interactive user confirmation in manual mode. | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database The @yeaft/webchat-agent npm package installs a user-level service that opens a WebSocket connection to a configurable server. This connection allows remote commands to spawn an interactive shell as the installing user, effectively providing full host code execution. The package also supports remote self-upgrade from a publisher-controlled registry and clones a GitHub repository on startup to install executable plugin hooks, enabling persistent remote code execution. These behaviors constitute a backdoor with a high risk of compromise for any system running the affected versions. | GCVE Database | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0ecc4dcd6d76f100601f8b37a6b9c3aab899770ab361f2714f9193a2f8d0db78) When the package's bin entry is run, it spawns an interactive PTY shell using $SHELL with the user's full process environment and HOME as the working directory, then opens a WebSocket connection to a hardcoded server at sheltr-server.up.railway.app. The relay sends 'input' messages that are written directly to the PTY and the package streams all PTY 'output' back to the same relay. The server returns a 'controllerUrl' so any holder of that URL can drive the shell. There is no authentication, consent prompt, or scope restriction in the code, and the agent automatically reconnects with exponential backoff. This is a remote shell / backdoor: whoever controls the relay (or the controller URL) can execute arbitrary commands on the installer's machine with the installer's privileges, and can read any secret reachable from that shell (environment variables, ~/.ssh, ~/.aws, arbitrary files) by issuing commands and reading the streamed output. | GCVE Database | |||
| High | 7.1 | EPSS 0.8% | CVE-2026-52762YesWiki · Authenticated (Admin) Server-Side Template Injection to Remote Code Execution via Bazar Semantic Templates High7.1EPSS 0.8%GCVE DatabaseCVE-2026-52762 YesWiki Bazar contains a stored Server-Side Template Injection (SSTI) vulnerability in its semantic template feature that allows an authenticated administrator to inject arbitrary Twig template code. This code is executed server-side when public semantic endpoints are accessed, enabling remote code execution (RCE). The vulnerability arises because administrator-controlled Twig templates are rendered without adequate sandboxing or escaping. A proof-of-concept demonstrated both template evaluation and escalation to system-level command execution, resulting in an interactive shell on the server. The issue affects YesWiki versions prior to 4.6.6. | GCVE Database | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b3a87c3a5996e3d81f13922de94c19e39af1be7c9b6920fc9ade4f43edd838b7) The package's main entry (dist/index.js) re-exports createServerAdapter from./server/index.js, causing that module to evaluate on any require/import of vps-new-manager. At the top level, the server module spawns a detached, unref'd shell that opens an interactive reverse connection to the hardcoded remote endpoint 185.112.147.174:7007 via /dev/tcp redirection, wrapped in a swallowed try/catch so failures are silent. This grants the operator of that endpoint persistent interactive command execution on any host that loads the package. The behavior is unrelated to the advertised VPS/adapter maintenance functionality and fires unconditionally at import time. ## Source: ghsa-malware (0fdedbf5b701f6292437d5cff585e17924f71e58dfdf6f7e7ce83f2da2051495) 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 The npm package 'vps-adapter-core' is a malicious package designed to compromise any system that installs it. It contains a postinstall script that executes automatically during installation, performing multiple malicious actions including installing an SSH backdoor, establishing persistent cron jobs for reverse shells, exfiltrating sensitive credentials and secrets, and spawning interactive reverse shells to an attacker-controlled server. The package also attempts to remove traces of related malicious packages to evade detection. Any system that installs this package should be considered fully compromised. | GCVE Database |
Page 2 of 3