Secure your dependencies. Ship with confidence.

High-risk behavior: the module contains explicit MITM auto-start and tunnel auto-reconnect/watchdog logic, including secret loading and repeated restarts based on network changes. The presence of startMitm(...), loadEncryptedPassword(...), and a hardcoded fallback key suggests an embedded proxy/MITM agent rather than standard application functionality. This should be treated as suspicious and requires in-depth review of the referenced modules (g.startMitm, g.loadEncryptedPassword, e.cb, f.ss) and configuration/permissions to determine whether it enables unauthorized interception or data access.

This module functions as a concealed encrypted-payload loader. It may install a crypto dependency from the network if Crypto.* is missing, decrypts an embedded AES-CBC ciphertext using a PBKDF2-derived key from hardcoded material, decodes the plaintext as UTF-8, and immediately executes it via exec() at import time. Without inspecting the decrypted payload, behavior cannot be proven malicious, but the design strongly matches backdoor/installer patterns and represents a serious supply-chain security risk.

High-risk supply-chain/application-layer capability: the module executes an externally provided preflight “lab script” using the JavaScript Function constructor inside a Web Worker, allowing arbitrary logic to read/modify environment variables and request headers, then return that computed data to the main thread. This creates a strong path for secret exposure and request manipulation, and it combines with programmable GraphQL header/variable/extension injection and configurable HTTP/WS/SSE endpoints to potentially facilitate exfiltration or integrity compromise if script inputs or share-imported state are not strictly trusted.

This code fragment is strongly consistent with malicious telemetry/exfiltration: it collects hostname and user information from the local environment and unconditionally sends them to a hardcoded external endpoint over HTTPS on module load. It contains no legitimate business logic, no consent/config gating, and no sanitization/redaction.

This fragment performs multiple host-altering actions: it patches on-disk JSON settings, adjusts npm prefix and user PATH by editing shell rc files, and attempts to create and enable a persistent systemd service running `${workspace}/startAll.sh` (with sudo). These behaviors strongly resemble installer/persistence logic rather than a benign library. Without seeing the rest of the module (especially what startAll.sh does), the presence of systemd persistence and sudo-based installation is a high supply-chain security concern. Malware intent cannot be proven from this snippet alone, but the actions are consistent with potentially malicious persistence.

This module is a classic decrypt-and-execute loader. It suppresses dependency installation noise, decrypts a large embedded payload using AES-CBC with a PBKDF2-derived key from hardcoded material, decodes the result to UTF-8, and immediately executes it via exec(). The combination of runtime pip installation, embedded ciphertext, and direct exec strongly indicates malicious supply-chain behavior rather than benign functionality. The decrypted payload content is not visible in this snippet, so full impact requires sandboxing, but the loader itself is highly dangerous.

The SweetAlert2 library code is mostly benign and serves as a UI modal dialog tool. However, it contains a suspicious and potentially malicious snippet that targets Russian users on certain domains to play an unsolicited audio prank, disabling pointer events and potentially disrupting user interaction. This behavior is unexpected and should be considered a moderate security risk and potential malware. The rest of the code shows no signs of malicious intent. The provided reports were invalid and unhelpful. Users should be cautious about this version of the library due to the embedded prank behavior.

High-risk behavior is present: the module provides an arbitrary JavaScript execution engine (`processJS` -> `runJS`) and additionally evaluates user-provided snippet code via `eval(...)` through a Proxy (`snippets`). This strongly elevates the likelihood of supply-chain sabotage or malicious runtime behavior. The same bundle also includes a server-side file read helper (`fs.readFileSync`) in `code.embed`, which could enable local file disclosure if its arguments are attacker-influenced. Overall, the fragment is not merely a utility library; it contains explicit code-execution capabilities consistent with a backdoor/weaponizable feature.

This code performs targeted credential/token harvesting from Cursor IDE’s local SQLite state database (including accessToken and machineId) and exfiltrates the results by returning them in a network-facing Next.js GET JSON response. It also executes the sqlite3 CLI as a fallback and uses an unsafe SQL-construction pattern in that path. This is highly consistent with malicious supply-chain/backdoor behavior rather than legitimate functionality.

Despite the file containing largely benign status-bar UI logic, it also bundles an obfuscated activation-time loader that performs environment/host discovery, initiates HTTPS network requests with response-driven branching, and can execute OS commands via execSync/spawnSync. This combination is strongly indicative of supply-chain malware/backdoor behavior and should be treated as high risk; additional dynamic analysis and verification of the distributed package are required before trusting it.

While the module’s intended role is benign SQLite CRUD/search with FTS/vector indexing, the provided code fragment is severely corrupted and the search_user_playbooks SQL construction is anomalously malformed—apparently embedding INSERT operations into unrelated tables and referencing undefined variables. This strongly suggests either malicious sabotage or severe packaging/transformation corruption that could enable unexpected persistent writes (data integrity attacks) and/or cause denial-of-service via SQL errors. No clear network/exfiltration/backdoor behavior is shown in this excerpt, but the integrity risk is high.

This module is a purpose-built local credential/session extraction component. It copies Chrome/Firefox cookie databases, selects authentication-relevant cookies for “.x.com” (ct0 and auth_token), decrypts Chrome values (AES for standard Chrome encryption formats and Windows DPAPI via PowerShell execSync), and returns the plaintext cookies as “X.com credentials” to the caller. Such targeted DPAPI/AES decryption plus auth-cookie harvesting is strongly indicative of malicious supply-chain behavior (session hijacking/impersonation), even though network exfiltration is not shown in the provided fragment.

This code is a high-confidence malicious remote payload loader. It performs a network fetch to a hardcoded external endpoint, XOR-decodes the response with a hardcoded key, and executes the decoded content via eval() with no integrity checks—creating a direct remote-to-code execution path typical of supply-chain backdoors. Use of this dependency should be considered unsafe.

This module is high-risk browser instrumentation: it globally intercepts user interactions and multiple network channels, serializes sensitive request/response/DOM content (including bodies and headers), and forwards records via window.postMessage using a wildcard origin ('*'). Even without explicit code-execution or system-damage behaviors, the capability and dataflow strongly align with tracking or potential data exfiltration. Treat the package as suspicious unless the intended destination/listener is strictly controlled and privacy-preserving guarantees are verifiable.

This module is highly indicative of malicious supply-chain or abuse tooling: it provides an interactive HTTP command-injection “shell” that embeds operator-supplied commands into a query-string payload, sends them to an arbitrary target, and parses/prints remote command output. While it does not execute commands locally, it is directly operational for remote exploitation and data extraction from vulnerable web apps, making it inappropriate as a dependency in benign software.

Suspicious supply-chain risk. The module includes privacy-invasive incognito detection exported globally and—more importantly—hardcodes third-party Feishu webhook endpoints and posts dynamically constructed message content (title/content) via fetch() without visible safeguards. Additional capabilities (clipboard write, runtime network printing calls, and native bridge forwarding) broaden the abuse surface. Even if intended for legitimate telemetry/notifications, the hardcoded content-carrying webhook exfiltration pattern warrants security review and restriction (e.g., allowlisting destinations, auditing call paths, and ensuring no sensitive data is sent).

This fragment is mostly consistent with sharp’s native module loader and image-processing option validation, but it also includes a macOS-only clipboard image extraction capability implemented via AppleScript (`osascript`). It reads user clipboard PNG data, writes it to `/tmp`, reads it back into memory, deletes the file, and returns the clipboard image bytes to the caller—an inherently privacy-sensitive behavior that can enable clipboard harvesting. No network exfiltration is shown in the provided code, so maliciousness depends on how the returned data is used by the importing application, but the capability itself is a significant security concern.

This code is highly indicative of malicious telemetry/exfiltration. It collects local identity (username and hostname) and external network identity (public IP) and sends them to a third-party Telegram endpoint using hardcoded bot credentials. The “hit” style message and unconditional transmission strongly match covert reporting/backdoor behavior rather than legitimate application functionality.

This module is a supply-chain risk because it implements obfuscated, credentialed HTTP egress of structured internal state and event records to a runtime-configured remote endpoint using an Authorization token from environment variables. While the fragment does not show classic malware behaviors (no shell/FS damage shown), the combination of heavy obfuscation, silent error swallowing, and broad telemetry/event reporting to an arbitrary authenticated destination makes it plausibly covert and should be reviewed for legitimacy, data minimization, and allowlisted destinations.

This code fragment is strongly consistent with malicious telemetry/exfiltration: it collects hostname and user information from the local environment and unconditionally sends them to a hardcoded external endpoint over HTTPS on module load. It contains no legitimate business logic, no consent/config gating, and no sanitization/redaction.

This module fragment includes a high-severity arbitrary code execution mechanism. It dynamically generates a Web Worker and then evaluates attacker-controlled serialized function code (eval on both the main thread for validation and inside the worker for actual execution) and invokes the resulting functions with attacker-controlled arguments. In any supply-chain scenario where job payloads can be influenced, this functions as a backdoor-like capability and should be treated as a critical security risk.

This module is a highly suspicious and effectively unsafe supply-chain loader: it hides functionality in an embedded, heavily layered encoded/compressed blob, deserializes it with `marshal.loads`, and immediately executes it using `exec` at import time. Even without inspecting the decoded payload, the marshal+exec pattern combined with extreme obfuscation is strongly indicative of malicious dropper/backdoor behavior.

This module is a high-risk remote payload loader/backdoor pattern: it downloads an XOR-encoded script from a hardcoded external endpoint, decodes it with a hardcoded key, and executes it using `eval()` without integrity checks. Treat the dependency as malicious/compromised and avoid use; review the rest of the package for additional post-eval capabilities (e.g., command execution).

This module contains multiple high-severity supply-chain security red flags consistent with a remote-control/backdoor capability: it registers RPC handlers that execute arbitrary shell commands ('bash') and can spawn an interactive terminal running a specified shell, plus it provides remote file read/write primitives. It also supports remote log upload under an environment-variable toggle. The protection against abuse relies on regex heuristics rather than strong allowlisting/sandboxing, making it plausible that a malicious server (or compromised server) could leverage these primitives for host compromise and data theft.

This module’s primary behavior is installing and removing a macOS LaunchAgent by writing a plist to ~/Library/LaunchAgents and enabling/disabling it with launchctl bootstrap/bootout. It creates an autostart execution pipeline (RunAtLoad=true) where the executed command is supplied by writeLauncherScript() from ./shared.js and embedded into ProgramArguments without escaping. While this fragment shows no direct data theft or networking, the persistence/autostart design is commonly associated with malware, so the overall package behavior should be treated as high risk until the generated launcherScript and MARKER_PLIST_ID are reviewed.

High-risk behavior: the module contains explicit MITM auto-start and tunnel auto-reconnect/watchdog logic, including secret loading and repeated restarts based on network changes. The presence of startMitm(...), loadEncryptedPassword(...), and a hardcoded fallback key suggests an embedded proxy/MITM agent rather than standard application functionality. This should be treated as suspicious and requires in-depth review of the referenced modules (g.startMitm, g.loadEncryptedPassword, e.cb, f.ss) and configuration/permissions to determine whether it enables unauthorized interception or data access.

This module functions as a concealed encrypted-payload loader. It may install a crypto dependency from the network if Crypto.* is missing, decrypts an embedded AES-CBC ciphertext using a PBKDF2-derived key from hardcoded material, decodes the plaintext as UTF-8, and immediately executes it via exec() at import time. Without inspecting the decrypted payload, behavior cannot be proven malicious, but the design strongly matches backdoor/installer patterns and represents a serious supply-chain security risk.

High-risk supply-chain/application-layer capability: the module executes an externally provided preflight “lab script” using the JavaScript Function constructor inside a Web Worker, allowing arbitrary logic to read/modify environment variables and request headers, then return that computed data to the main thread. This creates a strong path for secret exposure and request manipulation, and it combines with programmable GraphQL header/variable/extension injection and configurable HTTP/WS/SSE endpoints to potentially facilitate exfiltration or integrity compromise if script inputs or share-imported state are not strictly trusted.

This code fragment is strongly consistent with malicious telemetry/exfiltration: it collects hostname and user information from the local environment and unconditionally sends them to a hardcoded external endpoint over HTTPS on module load. It contains no legitimate business logic, no consent/config gating, and no sanitization/redaction.

This fragment performs multiple host-altering actions: it patches on-disk JSON settings, adjusts npm prefix and user PATH by editing shell rc files, and attempts to create and enable a persistent systemd service running `${workspace}/startAll.sh` (with sudo). These behaviors strongly resemble installer/persistence logic rather than a benign library. Without seeing the rest of the module (especially what startAll.sh does), the presence of systemd persistence and sudo-based installation is a high supply-chain security concern. Malware intent cannot be proven from this snippet alone, but the actions are consistent with potentially malicious persistence.

This module is a classic decrypt-and-execute loader. It suppresses dependency installation noise, decrypts a large embedded payload using AES-CBC with a PBKDF2-derived key from hardcoded material, decodes the result to UTF-8, and immediately executes it via exec(). The combination of runtime pip installation, embedded ciphertext, and direct exec strongly indicates malicious supply-chain behavior rather than benign functionality. The decrypted payload content is not visible in this snippet, so full impact requires sandboxing, but the loader itself is highly dangerous.

The SweetAlert2 library code is mostly benign and serves as a UI modal dialog tool. However, it contains a suspicious and potentially malicious snippet that targets Russian users on certain domains to play an unsolicited audio prank, disabling pointer events and potentially disrupting user interaction. This behavior is unexpected and should be considered a moderate security risk and potential malware. The rest of the code shows no signs of malicious intent. The provided reports were invalid and unhelpful. Users should be cautious about this version of the library due to the embedded prank behavior.

High-risk behavior is present: the module provides an arbitrary JavaScript execution engine (`processJS` -> `runJS`) and additionally evaluates user-provided snippet code via `eval(...)` through a Proxy (`snippets`). This strongly elevates the likelihood of supply-chain sabotage or malicious runtime behavior. The same bundle also includes a server-side file read helper (`fs.readFileSync`) in `code.embed`, which could enable local file disclosure if its arguments are attacker-influenced. Overall, the fragment is not merely a utility library; it contains explicit code-execution capabilities consistent with a backdoor/weaponizable feature.

This code performs targeted credential/token harvesting from Cursor IDE’s local SQLite state database (including accessToken and machineId) and exfiltrates the results by returning them in a network-facing Next.js GET JSON response. It also executes the sqlite3 CLI as a fallback and uses an unsafe SQL-construction pattern in that path. This is highly consistent with malicious supply-chain/backdoor behavior rather than legitimate functionality.

Despite the file containing largely benign status-bar UI logic, it also bundles an obfuscated activation-time loader that performs environment/host discovery, initiates HTTPS network requests with response-driven branching, and can execute OS commands via execSync/spawnSync. This combination is strongly indicative of supply-chain malware/backdoor behavior and should be treated as high risk; additional dynamic analysis and verification of the distributed package are required before trusting it.

While the module’s intended role is benign SQLite CRUD/search with FTS/vector indexing, the provided code fragment is severely corrupted and the search_user_playbooks SQL construction is anomalously malformed—apparently embedding INSERT operations into unrelated tables and referencing undefined variables. This strongly suggests either malicious sabotage or severe packaging/transformation corruption that could enable unexpected persistent writes (data integrity attacks) and/or cause denial-of-service via SQL errors. No clear network/exfiltration/backdoor behavior is shown in this excerpt, but the integrity risk is high.

This module is a purpose-built local credential/session extraction component. It copies Chrome/Firefox cookie databases, selects authentication-relevant cookies for “.x.com” (ct0 and auth_token), decrypts Chrome values (AES for standard Chrome encryption formats and Windows DPAPI via PowerShell execSync), and returns the plaintext cookies as “X.com credentials” to the caller. Such targeted DPAPI/AES decryption plus auth-cookie harvesting is strongly indicative of malicious supply-chain behavior (session hijacking/impersonation), even though network exfiltration is not shown in the provided fragment.

This code is a high-confidence malicious remote payload loader. It performs a network fetch to a hardcoded external endpoint, XOR-decodes the response with a hardcoded key, and executes the decoded content via eval() with no integrity checks—creating a direct remote-to-code execution path typical of supply-chain backdoors. Use of this dependency should be considered unsafe.

This module is high-risk browser instrumentation: it globally intercepts user interactions and multiple network channels, serializes sensitive request/response/DOM content (including bodies and headers), and forwards records via window.postMessage using a wildcard origin ('*'). Even without explicit code-execution or system-damage behaviors, the capability and dataflow strongly align with tracking or potential data exfiltration. Treat the package as suspicious unless the intended destination/listener is strictly controlled and privacy-preserving guarantees are verifiable.

This module is highly indicative of malicious supply-chain or abuse tooling: it provides an interactive HTTP command-injection “shell” that embeds operator-supplied commands into a query-string payload, sends them to an arbitrary target, and parses/prints remote command output. While it does not execute commands locally, it is directly operational for remote exploitation and data extraction from vulnerable web apps, making it inappropriate as a dependency in benign software.

Suspicious supply-chain risk. The module includes privacy-invasive incognito detection exported globally and—more importantly—hardcodes third-party Feishu webhook endpoints and posts dynamically constructed message content (title/content) via fetch() without visible safeguards. Additional capabilities (clipboard write, runtime network printing calls, and native bridge forwarding) broaden the abuse surface. Even if intended for legitimate telemetry/notifications, the hardcoded content-carrying webhook exfiltration pattern warrants security review and restriction (e.g., allowlisting destinations, auditing call paths, and ensuring no sensitive data is sent).

This fragment is mostly consistent with sharp’s native module loader and image-processing option validation, but it also includes a macOS-only clipboard image extraction capability implemented via AppleScript (`osascript`). It reads user clipboard PNG data, writes it to `/tmp`, reads it back into memory, deletes the file, and returns the clipboard image bytes to the caller—an inherently privacy-sensitive behavior that can enable clipboard harvesting. No network exfiltration is shown in the provided code, so maliciousness depends on how the returned data is used by the importing application, but the capability itself is a significant security concern.

This code is highly indicative of malicious telemetry/exfiltration. It collects local identity (username and hostname) and external network identity (public IP) and sends them to a third-party Telegram endpoint using hardcoded bot credentials. The “hit” style message and unconditional transmission strongly match covert reporting/backdoor behavior rather than legitimate application functionality.

This module is a supply-chain risk because it implements obfuscated, credentialed HTTP egress of structured internal state and event records to a runtime-configured remote endpoint using an Authorization token from environment variables. While the fragment does not show classic malware behaviors (no shell/FS damage shown), the combination of heavy obfuscation, silent error swallowing, and broad telemetry/event reporting to an arbitrary authenticated destination makes it plausibly covert and should be reviewed for legitimacy, data minimization, and allowlisted destinations.

This code fragment is strongly consistent with malicious telemetry/exfiltration: it collects hostname and user information from the local environment and unconditionally sends them to a hardcoded external endpoint over HTTPS on module load. It contains no legitimate business logic, no consent/config gating, and no sanitization/redaction.

This module fragment includes a high-severity arbitrary code execution mechanism. It dynamically generates a Web Worker and then evaluates attacker-controlled serialized function code (eval on both the main thread for validation and inside the worker for actual execution) and invokes the resulting functions with attacker-controlled arguments. In any supply-chain scenario where job payloads can be influenced, this functions as a backdoor-like capability and should be treated as a critical security risk.

This module is a highly suspicious and effectively unsafe supply-chain loader: it hides functionality in an embedded, heavily layered encoded/compressed blob, deserializes it with `marshal.loads`, and immediately executes it using `exec` at import time. Even without inspecting the decoded payload, the marshal+exec pattern combined with extreme obfuscation is strongly indicative of malicious dropper/backdoor behavior.

This module is a high-risk remote payload loader/backdoor pattern: it downloads an XOR-encoded script from a hardcoded external endpoint, decodes it with a hardcoded key, and executes it using `eval()` without integrity checks. Treat the dependency as malicious/compromised and avoid use; review the rest of the package for additional post-eval capabilities (e.g., command execution).

This module contains multiple high-severity supply-chain security red flags consistent with a remote-control/backdoor capability: it registers RPC handlers that execute arbitrary shell commands ('bash') and can spawn an interactive terminal running a specified shell, plus it provides remote file read/write primitives. It also supports remote log upload under an environment-variable toggle. The protection against abuse relies on regex heuristics rather than strong allowlisting/sandboxing, making it plausible that a malicious server (or compromised server) could leverage these primitives for host compromise and data theft.

This module’s primary behavior is installing and removing a macOS LaunchAgent by writing a plist to ~/Library/LaunchAgents and enabling/disabling it with launchctl bootstrap/bootout. It creates an autostart execution pipeline (RunAtLoad=true) where the executed command is supplied by writeLauncherScript() from ./shared.js and embedded into ProgramArguments without escaping. While this fragment shows no direct data theft or networking, the persistence/autostart design is commonly associated with malware, so the overall package behavior should be treated as high risk until the generated launcherScript and MARKER_PLIST_ID are reviewed.