Secure your dependencies. Ship with confidence.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is not a benign dependency. It implements multi-service credential login/account probing, extracts and returns sensitive authentication artifacts (cookies/access tokens) and even the supplied passwords, and contains a clear remote-code-execution staging mechanism (file upload to a paste service + generated Python script executing fetched remote content via exec). Treat as high-risk malware/tooling: avoid inclusion and assume it enables unauthorized access and weaponization.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is highly consistent with malicious exploitation/credential theft: it deploys a VM startup script that queries the GCE metadata server for service account token/scopes/email and exfiltrates them to an arbitrary external URL. It also supports deploying arbitrary attacker-provided startup scripts from local files to execute on VM boot. For supply-chain risk, treat this as dangerous and unsuitable for untrusted environments without strong authorization and sandboxing.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

In this fragment, the dominant security signal is architectural: it spawns a detached, stdio-ignored Node child process and forwards JSON-stringified runtime inputs to that child. There is no direct evidence of malware, exfiltration, or credential theft in the shown code, but the actual risk depends heavily on the unseen ./lib/caller.js implementation. The detached/hidden execution model is a notable supply-chain risk area and warrants thorough review of the child script and argument handling.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This PHP module is a high-impact deployment/backdoor-like supply-chain component: it persists a bearer token, drops an authenticated upload/rollback PHP endpoint, accepts attacker-controlled ZIP archives, extracts them, and deploys their contents into the server root with aggressive cleanup. While it does not use direct code execution primitives, it enables remote code placement (and potentially RCE/webshell deployment) if the authorization token is exposed/compromised. It also uses self-deletion and lacks explicit validation of ZIP archive entries, which further increases risk.

This code is strongly indicative of credential-stealing malware in a supply-chain context: it harvests multiple sensitive environment variables (GitHub/AWS/NPM/GCP-related secrets) and exfiltrates them in full via an HTTPS POST to a hardcoded (Base64-obfuscated) external webhook, including host metadata. Immediate execution and suppressed errors further support malicious intent.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

High-risk remote control/surveillance behavior: the code starts an HTTP server on 0.0.0.0 that allows a client to navigate a persistent browser, execute attacker-supplied code in the page (page.evaluate with request-provided script), and capture/return screenshots and drive host mouse/keyboard via xdotool/AutoHotkey. This strongly matches spyware/remote access tool functionality rather than a benign library.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is more than a Slack API client: it includes a high-sensitivity credential import/decryption workflow targeting Slack Desktop local storage and (on macOS) the OS keychain to obtain and decrypt session cookie material, then persists tokens/cookies locally and uses them to perform broad Slack API operations (message retrieval, drafts, sending). Even if the destination is Slack’s API, the local credential-harvesting and persistence pattern is strongly consistent with malicious or takeover-adjacent behavior in a supply-chain context. Treat as high risk and require strict provenance review and sandboxing/permission controls before use.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is strongly consistent with intentional mDNS/DNS poisoning/spoofing: it joins mDNS multicast, parses incoming DNS questions, and—when configured filters allow and analysis mode is disabled—sends crafted A/AAAA responses with rdata set to configured IPv4/IPv6 addresses. Such behavior can redirect local name resolution and enable MITM or service redirection on the local network. No obfuscation or post-processing malware (e.g., exfiltration/backdoor) is evident in this fragment, but the implemented deception capability is itself a major security risk.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is not a benign dependency. It implements multi-service credential login/account probing, extracts and returns sensitive authentication artifacts (cookies/access tokens) and even the supplied passwords, and contains a clear remote-code-execution staging mechanism (file upload to a paste service + generated Python script executing fetched remote content via exec). Treat as high-risk malware/tooling: avoid inclusion and assume it enables unauthorized access and weaponization.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is highly consistent with malicious exploitation/credential theft: it deploys a VM startup script that queries the GCE metadata server for service account token/scopes/email and exfiltrates them to an arbitrary external URL. It also supports deploying arbitrary attacker-provided startup scripts from local files to execute on VM boot. For supply-chain risk, treat this as dangerous and unsuitable for untrusted environments without strong authorization and sandboxing.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

In this fragment, the dominant security signal is architectural: it spawns a detached, stdio-ignored Node child process and forwards JSON-stringified runtime inputs to that child. There is no direct evidence of malware, exfiltration, or credential theft in the shown code, but the actual risk depends heavily on the unseen ./lib/caller.js implementation. The detached/hidden execution model is a notable supply-chain risk area and warrants thorough review of the child script and argument handling.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This PHP module is a high-impact deployment/backdoor-like supply-chain component: it persists a bearer token, drops an authenticated upload/rollback PHP endpoint, accepts attacker-controlled ZIP archives, extracts them, and deploys their contents into the server root with aggressive cleanup. While it does not use direct code execution primitives, it enables remote code placement (and potentially RCE/webshell deployment) if the authorization token is exposed/compromised. It also uses self-deletion and lacks explicit validation of ZIP archive entries, which further increases risk.

This code is strongly indicative of credential-stealing malware in a supply-chain context: it harvests multiple sensitive environment variables (GitHub/AWS/NPM/GCP-related secrets) and exfiltrates them in full via an HTTPS POST to a hardcoded (Base64-obfuscated) external webhook, including host metadata. Immediate execution and suppressed errors further support malicious intent.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

High-risk remote control/surveillance behavior: the code starts an HTTP server on 0.0.0.0 that allows a client to navigate a persistent browser, execute attacker-supplied code in the page (page.evaluate with request-provided script), and capture/return screenshots and drive host mouse/keyboard via xdotool/AutoHotkey. This strongly matches spyware/remote access tool functionality rather than a benign library.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is more than a Slack API client: it includes a high-sensitivity credential import/decryption workflow targeting Slack Desktop local storage and (on macOS) the OS keychain to obtain and decrypt session cookie material, then persists tokens/cookies locally and uses them to perform broad Slack API operations (message retrieval, drafts, sending). Even if the destination is Slack’s API, the local credential-harvesting and persistence pattern is strongly consistent with malicious or takeover-adjacent behavior in a supply-chain context. Treat as high risk and require strict provenance review and sandboxing/permission controls before use.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

This module is strongly consistent with intentional mDNS/DNS poisoning/spoofing: it joins mDNS multicast, parses incoming DNS questions, and—when configured filters allow and analysis mode is disabled—sends crafted A/AAAA responses with rdata set to configured IPv4/IPv6 addresses. Such behavior can redirect local name resolution and enable MITM or service redirection on the local network. No obfuscation or post-processing malware (e.g., exfiltration/backdoor) is evident in this fragment, but the implemented deception capability is itself a major security risk.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.

The /hack endpoint provides remote, user-controlled execution of recon/exploitation tooling and includes a critical bash -c fallback that evaluates attacker-controlled strings, turning the service into a remote command execution mechanism (even if containerized). Additionally, /leak returns hardcoded breach results marked as pwned=True without verification, suggesting deceptive/social-engineering intent. Overall, this module is high-risk and should be treated as unsafe to deploy; remove the bash -c fallback, enforce strict authentication/authorization, and restrict execution to a narrowly validated allowlist without returning raw stderr/stdout to clients.