Secure OSS Dependencies
Beyond CVE Scanning
Open source code makes up more than 90% of modern software projects, with many apps spamming 10,000+ dependencies. This makes it easy for attackers to use open source as a vector for attacks where open source packages registries are frequently the target of malware. Traditional vulnerability scanners cannot detect active supply chain attacks. Socket's free GitHub app safeguards your open source code from both vulnerable and malicious dependencies.

@arcforge/axon
2.0.245
by codywakeford
Live on npm
Blocked by Socket
The fragment primarily implements Angular parsing and compiler AST utilities, with no visible credential theft, exfiltration, or remote-control behavior. However, numerous transformation routines explicitly replace AST expressions and values with undefined, strongly indicating sabotage that can disrupt or break compilation; the displayed parser section also appears malformed. Severity is high for functionality integrity, while no malicious network destination or credential target is present in the reviewed code.
github.com/W181496/MY-CTF-Challenges
v0.0.0-20231010165229-3165504af7c9
Live on go
Blocked by Socket
This PHP fragment is a staged decode/disclosure workflow: it fetches an attacker-influenced payload over HTTP, extracts an encoded blob from the response, writes it to /tmp/tmp, inflates/decodes it via php://filter, and echoes the result. The crafted request strongly implies targeting a sensitive file such as config.php, making the behavior consistent with malicious secret extraction/disclosure. If present in a dependency, it warrants immediate removal and investigation.
github.com/nccgroup/singularity
v0.0.0-20261120062225-3f7e94358921
Live on go
Blocked by Socket
The code implements a flood/DoS-like pattern by launching a large number of outbound HTTP requests to dynamically constructed hostnames. It uses a worker-based message handler to receive parameters (hostname, port, iterations) and performs a burst of fetch operations without handling responses. While not exhibiting explicit data exfiltration or backdoors, this behavior is malicious in contexts where it is used to overwhelm a target or violate terms of service.
github.com/slicingmelon/GoBypass403
v0.8.7
Live on go
Blocked by Socket
This is an intentionally offensive payload-generation module, not a benign URL transformer. It constructs large sets of exploit-ready URIs designed to bypass Nginx/proxy ACLs via encoded newline + HTTP version injection, malformed normalization edge cases, and embedded scheme/host routing patterns (including localhost and non-HTTP schemes). It can also set the Host header in returned payloads. While it does not directly exfiltrate data or execute commands within this fragment, its purpose and output strongly indicate high risk for misuse in authenticated or unauthorized scanning/exploitation workflows.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123065341-91279bff2618
Live on go
Blocked by Socket
This fragment defines configuration and state for an agent described as communicating with a C2 server, supporting SOCKS5 proxying, reverse-shell transport, and process injection for persistence. These are strong malware indicators, but the fragment itself performs no such actions and provides no C2 address, URL, domain, IP, file path, or targeted credentials. Severity is elevated because of the explicit agent and persistence intent; assess the surrounding package before use.
subscraper-extension@matias.local
1.0.21
by anonymous-8b7916cb6aabf835cfa9c2878d007c60
Live on firefox
Blocked by Socket
The excerpt contains an authentication relay that POSTs userId, sess, xBc, and user-agent data to AUTH_RELAY_URL, making transmission of session credentials the primary security concern; the destination is not visible here and cannot be verified. It also uses sess in a declarative cookie rule and exposes download and CDN-rule operations without explicit sender checks in the shown branches. These behaviors may serve the extension's stated OnlyFans functionality, but the credential relay and request authorization should be reviewed before trust; severity is high if the relay destination is not an explicitly trusted service.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123094136-63cd9914d9d0
Live on go
Blocked by Socket
This is an emp3r0r command-and-control agent component, not a general-purpose utility: it fingerprints the host, can report tunnel data to its configured controller, accepts a peer instruction to terminate, and downloads and executes replacement agents. The upgrade is staged beneath RuntimeConfig.AgentRoot and launched with REPLACE_AGENT=true; the controller address and download endpoint are runtime-configured, with the comment identifying an /agent endpoint, while connectivity testing uses tun.UbuntuConnectivityURL. These are explicit remote-management and reconnaissance capabilities; checksum validation does not independently authenticate the download source. Severity is high if this code is present or run without authorization; no literal domain, IP, or credential target appears in this fragment.
github.com/oracle/docker-images
v0.0.0-20261119175845-e8be1c6e0738
Live on go
Blocked by Socket
This looks like an installation/bootstrap script that performs standard directory setup and environment persistence, but it also makes a very high-impact system change: it appends a hardcoded unrestricted passwordless sudo rule for the user 'oracle' to /etc/sudoers. It additionally weakens /etc/sudoers permissions to 666 before modifying it, creating a tampering window. Even if intended for a controlled provisioning scenario, this behavior is strongly suspicious from a supply-chain security perspective because it grants persistent, broad administrative access.
github.com/bitboxswiss/bitbox02-firmware
v0.0.0-20261119142730-70a32f5bbf6c
Live on go
Blocked by Socket
High severity: this code embeds a fixed recovery phrase, prints it to standard output, and returns it to every caller of get_with_language, creating a direct wallet-credential exposure risk. The confirmation function also reports success without user interaction and prints supplied mnemonic words. No network indicators, file paths, environment variables, or other credential types are present in the fragment. The code is readable and not obfuscated; the fixed phrase may be a test stub, but it must not be used for real recovery.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20261120044915-f51c6aa83ed4
Live on go
Blocked by Socket
This is a purpose-built C2 transport component with certificate pinning-to-CA-style trust and optional camouflage/routing features. It does not itself show host-data theft or destructive behavior, but its C2 communication functionality is a strong malicious-use indicator in an otherwise untrusted package. Plain HTTP configuration would expose traffic to interception.
pinokiod
8.3.26
by cocktailpeanut
Live on npm
Blocked by Socket
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.
github.com/ORACLE/DOCKER-IMAGES
v0.0.0-20261119175845-e8be1c6e0738
Live on go
Blocked by Socket
This looks like an installation/bootstrap script that performs standard directory setup and environment persistence, but it also makes a very high-impact system change: it appends a hardcoded unrestricted passwordless sudo rule for the user 'oracle' to /etc/sudoers. It additionally weakens /etc/sudoers permissions to 666 before modifying it, creating a tampering window. Even if intended for a controlled provisioning scenario, this behavior is strongly suspicious from a supply-chain security perspective because it grants persistent, broad administrative access.
github.com/nccgroup/singularity
v0.0.0-20261120063628-00a04fbaf541
Live on go
Blocked by Socket
This Go module is highly indicative of malicious/offensive functionality: it implements DNS rebinding session state, crafts DNS responses to redirect clients, conditionally disrupts browser connections via iptables during multi-A rebinding, and serves an HTML page that embeds/executes multiple browser attack payloads automatically. While there are no obvious classic memory safety issues in this fragment, the overall behavior constitutes an attack framework suitable for unauthorized intrusion or service exploitation.
github.com/utisss/utctf-2022
v0.0.0-20220315173045-79601865b2af
Live on go
Blocked by Socket
High-risk internal automation pattern. This module sets a sensitive environment-derived secret (process.env.FLAG) into a cookie for an internal localhost origin, then uses Puppeteer request interception to transform an internal browser request into a POST carrying attacker-controlled content from req.body.image. While there is no explicit remote exfiltration shown, the combination of secret injection plus attacker-controlled internal request manipulation creates a serious risk of internal secret leakage or abuse of localhost application logic. The '--no-sandbox' setting further increases the impact of potential browser compromise. Review the internal '/' handler’s processing of the 'image' form parameter and cookie usage, and avoid running privileged headless automation on untrusted input without strict isolation and allowlisting.
github.com/nccgroup/singularity
v0.0.0-20261120062225-3f7e94358921
Live on go
Blocked by Socket
High risk of data leakage and backdoor-like behavior. The code intentionally leverages Docker API to mount /etc and read /etc/shadow inside a container, then exposes the output through logs/attach responses. This is a clear pattern of host data exfiltration via a Docker-based sandbox and indicates potential malicious intent if used without explicit authorization. Recommend treating as a critical security risk and deprecating / removing or sandboxing this functionality.
github.com/nccgroup/singularity
v0.0.0-20261120063628-00a04fbaf541
Live on go
Blocked by Socket
High risk of data leakage and backdoor-like behavior. The code intentionally leverages Docker API to mount /etc and read /etc/shadow inside a container, then exposes the output through logs/attach responses. This is a clear pattern of host data exfiltration via a Docker-based sandbox and indicates potential malicious intent if used without explicit authorization. Recommend treating as a critical security risk and deprecating / removing or sandboxing this functionality.
github.com/ukgovernmentbeis/sandbox_escape_bench
v0.0.0-20261115144815-c07dc32601d8
Live on go
Blocked by Socket
This is an explicit container escape exploit, not ordinary application or build logic. It compiles and launches externally supplied exploit code, modifies /bin/sh, targets runc for binary overwrite, and is designed to execute a payload outside the container when subsequent docker exec operations occur. It should not be executed or included in a package.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20261120044915-f51c6aa83ed4
Live on go
Blocked by Socket
The fragment implements file I/O, but explicitly designs that I/O to evade Linux syscall-entry monitoring and discusses avoiding an environment-based detection vector. This is a significant defense-evasion indicator and warrants treating the code as high risk; no data exfiltration or other payload is visible in the supplied fragment.
github.com/W181496/MY-CTF-Challenges
v0.0.0-20231010165229-3165504af7c9
Live on go
Blocked by Socket
This module is an extremely dangerous Serializable deserialization gadget. When an attacker can cause Java deserialization to instantiate this class, its readResolve() method unconditionally spawns a bash process and base64-decodes and executes an interactive shell payload. The behavior matches malware backdoor/reverse-shell style command execution patterns and presents a critical supply-chain risk if included as a dependency.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123065341-91279bff2618
Live on go
Blocked by Socket
This is an emp3r0r command-and-control agent component, not a general-purpose utility: it fingerprints the host, can report tunnel data to its configured controller, accepts a peer instruction to terminate, and downloads and executes replacement agents. The upgrade is staged beneath RuntimeConfig.AgentRoot and launched with REPLACE_AGENT=true; the controller address and download endpoint are runtime-configured, with the comment identifying an /agent endpoint, while connectivity testing uses tun.UbuntuConnectivityURL. These are explicit remote-management and reconnaissance capabilities; checksum validation does not independently authenticate the download source. Severity is high if this code is present or run without authorization; no literal domain, IP, or credential target appears in this fragment.
github.com/W181496/MY-CTF-Challenges
v0.0.0-20231010165229-3165504af7c9
Live on go
Blocked by Socket
High-severity suspicious PHP code: it evaluates request-controlled data and uses the result to construct an outbound cURL URL, and a separate request parameter can read and disclose local file contents. It also exposes its source and includes config.php; no fixed domain, IP address, or credential target is visible. The dynamic evaluation and request-driven network behavior are strong indicators of a backdoor or unsafe concealed endpoint, though intent and the exact reachable payload depend on PHP runtime behavior and surrounding application context.
xueoj-vjtof-util
0.0.1-security
by npm
Live on npm
Blocked by Socket
Malicious code in xueoj-vjtof-util (npm) Source: amazon-inspector (6361a9939d5d4927d1ed0e68d74fc9173e377b0cd59b8734830c62e81fdb1a8e) index.js (the declared main entry) reads an undocumented _bz byte array (195 bytes beginning with the zlib magic 0x78 0x9c) from package.json, zlib-inflates it, and executes the decoded string via the Function constructor at require() time, running with full Node privileges in any process that imports the package. Execution is gated by an explicit early return when any of CI, GITHUB_ACTIONS, GITLAB_CI, TRAVIS, CIRCLECI, or SANDBOX environment variables is set, and errors are swallowed by a try/catch, so the payload fires only in developer or production environments and stays silent under common analysis contexts. Smuggling the executable blob as a numeric byte array inside package.json rather than a.js file hides it from file-level review and from scanners that only inspect JavaScript sources. The package exports nothing useful and is described generically as a 'utility', providing no legitimate reason for this pattern. Source: ghsa-malware (f33678f60adab8790527c4caf13ae874dbfc31c06492d0e96a564a8ccdeac181) 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.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123094136-63cd9914d9d0
Live on go
Blocked by Socket
This Linux-only code deliberately removes keyword-matching entries from /var/log/wtmp, /var/log/btmp, /var/log/utmp, and /var/log/auth.log or /var/log/secure, thereby enabling concealment of login or authentication activity. It also risks log loss because it replaces xtmp files before writing filtered data and can panic on a non-384-byte-aligned file. Severity is high for audit integrity; no network exfiltration or credential harvesting is present in the fragment.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123065341-91279bff2618
Live on go
Blocked by Socket
This code is a high-confidence Spring Cloud Gateway actuator remote-code-execution exploit. It sends a crafted route containing a Runtime.exec Spring expression, refreshes the gateway configuration, and retrieves command output. It should not be used except in a tightly authorized security test environment; deploying or running it against third-party systems would be unauthorized exploitation.
hydromind
5.24.8
Live on pypi
Blocked by Socket
This module is an import-time dynamic execution wrapper that uses a native extension (`hydromind._protection_native.exec_module`) to execute `hydromind.agent` within the importer’s `globals()` context. The design is atypical for benign dependencies and is a substantial security red flag in a supply-chain context, though concrete malicious behavior (e.g., network/file/persistence/credential theft) cannot be verified without reviewing `hydromind.agent` and the native implementation.
@arcforge/axon
2.0.245
by codywakeford
Live on npm
Blocked by Socket
The fragment primarily implements Angular parsing and compiler AST utilities, with no visible credential theft, exfiltration, or remote-control behavior. However, numerous transformation routines explicitly replace AST expressions and values with undefined, strongly indicating sabotage that can disrupt or break compilation; the displayed parser section also appears malformed. Severity is high for functionality integrity, while no malicious network destination or credential target is present in the reviewed code.
github.com/W181496/MY-CTF-Challenges
v0.0.0-20231010165229-3165504af7c9
Live on go
Blocked by Socket
This PHP fragment is a staged decode/disclosure workflow: it fetches an attacker-influenced payload over HTTP, extracts an encoded blob from the response, writes it to /tmp/tmp, inflates/decodes it via php://filter, and echoes the result. The crafted request strongly implies targeting a sensitive file such as config.php, making the behavior consistent with malicious secret extraction/disclosure. If present in a dependency, it warrants immediate removal and investigation.
github.com/nccgroup/singularity
v0.0.0-20261120062225-3f7e94358921
Live on go
Blocked by Socket
The code implements a flood/DoS-like pattern by launching a large number of outbound HTTP requests to dynamically constructed hostnames. It uses a worker-based message handler to receive parameters (hostname, port, iterations) and performs a burst of fetch operations without handling responses. While not exhibiting explicit data exfiltration or backdoors, this behavior is malicious in contexts where it is used to overwhelm a target or violate terms of service.
github.com/slicingmelon/GoBypass403
v0.8.7
Live on go
Blocked by Socket
This is an intentionally offensive payload-generation module, not a benign URL transformer. It constructs large sets of exploit-ready URIs designed to bypass Nginx/proxy ACLs via encoded newline + HTTP version injection, malformed normalization edge cases, and embedded scheme/host routing patterns (including localhost and non-HTTP schemes). It can also set the Host header in returned payloads. While it does not directly exfiltrate data or execute commands within this fragment, its purpose and output strongly indicate high risk for misuse in authenticated or unauthorized scanning/exploitation workflows.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123065341-91279bff2618
Live on go
Blocked by Socket
This fragment defines configuration and state for an agent described as communicating with a C2 server, supporting SOCKS5 proxying, reverse-shell transport, and process injection for persistence. These are strong malware indicators, but the fragment itself performs no such actions and provides no C2 address, URL, domain, IP, file path, or targeted credentials. Severity is elevated because of the explicit agent and persistence intent; assess the surrounding package before use.
subscraper-extension@matias.local
1.0.21
by anonymous-8b7916cb6aabf835cfa9c2878d007c60
Live on firefox
Blocked by Socket
The excerpt contains an authentication relay that POSTs userId, sess, xBc, and user-agent data to AUTH_RELAY_URL, making transmission of session credentials the primary security concern; the destination is not visible here and cannot be verified. It also uses sess in a declarative cookie rule and exposes download and CDN-rule operations without explicit sender checks in the shown branches. These behaviors may serve the extension's stated OnlyFans functionality, but the credential relay and request authorization should be reviewed before trust; severity is high if the relay destination is not an explicitly trusted service.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123094136-63cd9914d9d0
Live on go
Blocked by Socket
This is an emp3r0r command-and-control agent component, not a general-purpose utility: it fingerprints the host, can report tunnel data to its configured controller, accepts a peer instruction to terminate, and downloads and executes replacement agents. The upgrade is staged beneath RuntimeConfig.AgentRoot and launched with REPLACE_AGENT=true; the controller address and download endpoint are runtime-configured, with the comment identifying an /agent endpoint, while connectivity testing uses tun.UbuntuConnectivityURL. These are explicit remote-management and reconnaissance capabilities; checksum validation does not independently authenticate the download source. Severity is high if this code is present or run without authorization; no literal domain, IP, or credential target appears in this fragment.
github.com/oracle/docker-images
v0.0.0-20261119175845-e8be1c6e0738
Live on go
Blocked by Socket
This looks like an installation/bootstrap script that performs standard directory setup and environment persistence, but it also makes a very high-impact system change: it appends a hardcoded unrestricted passwordless sudo rule for the user 'oracle' to /etc/sudoers. It additionally weakens /etc/sudoers permissions to 666 before modifying it, creating a tampering window. Even if intended for a controlled provisioning scenario, this behavior is strongly suspicious from a supply-chain security perspective because it grants persistent, broad administrative access.
github.com/bitboxswiss/bitbox02-firmware
v0.0.0-20261119142730-70a32f5bbf6c
Live on go
Blocked by Socket
High severity: this code embeds a fixed recovery phrase, prints it to standard output, and returns it to every caller of get_with_language, creating a direct wallet-credential exposure risk. The confirmation function also reports success without user interaction and prints supplied mnemonic words. No network indicators, file paths, environment variables, or other credential types are present in the fragment. The code is readable and not obfuscated; the fixed phrase may be a test stub, but it must not be used for real recovery.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20261120044915-f51c6aa83ed4
Live on go
Blocked by Socket
This is a purpose-built C2 transport component with certificate pinning-to-CA-style trust and optional camouflage/routing features. It does not itself show host-data theft or destructive behavior, but its C2 communication functionality is a strong malicious-use indicator in an otherwise untrusted package. Plain HTTP configuration would expose traffic to interception.
pinokiod
8.3.26
by cocktailpeanut
Live on npm
Blocked by Socket
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.
github.com/ORACLE/DOCKER-IMAGES
v0.0.0-20261119175845-e8be1c6e0738
Live on go
Blocked by Socket
This looks like an installation/bootstrap script that performs standard directory setup and environment persistence, but it also makes a very high-impact system change: it appends a hardcoded unrestricted passwordless sudo rule for the user 'oracle' to /etc/sudoers. It additionally weakens /etc/sudoers permissions to 666 before modifying it, creating a tampering window. Even if intended for a controlled provisioning scenario, this behavior is strongly suspicious from a supply-chain security perspective because it grants persistent, broad administrative access.
github.com/nccgroup/singularity
v0.0.0-20261120063628-00a04fbaf541
Live on go
Blocked by Socket
This Go module is highly indicative of malicious/offensive functionality: it implements DNS rebinding session state, crafts DNS responses to redirect clients, conditionally disrupts browser connections via iptables during multi-A rebinding, and serves an HTML page that embeds/executes multiple browser attack payloads automatically. While there are no obvious classic memory safety issues in this fragment, the overall behavior constitutes an attack framework suitable for unauthorized intrusion or service exploitation.
github.com/utisss/utctf-2022
v0.0.0-20220315173045-79601865b2af
Live on go
Blocked by Socket
High-risk internal automation pattern. This module sets a sensitive environment-derived secret (process.env.FLAG) into a cookie for an internal localhost origin, then uses Puppeteer request interception to transform an internal browser request into a POST carrying attacker-controlled content from req.body.image. While there is no explicit remote exfiltration shown, the combination of secret injection plus attacker-controlled internal request manipulation creates a serious risk of internal secret leakage or abuse of localhost application logic. The '--no-sandbox' setting further increases the impact of potential browser compromise. Review the internal '/' handler’s processing of the 'image' form parameter and cookie usage, and avoid running privileged headless automation on untrusted input without strict isolation and allowlisting.
github.com/nccgroup/singularity
v0.0.0-20261120062225-3f7e94358921
Live on go
Blocked by Socket
High risk of data leakage and backdoor-like behavior. The code intentionally leverages Docker API to mount /etc and read /etc/shadow inside a container, then exposes the output through logs/attach responses. This is a clear pattern of host data exfiltration via a Docker-based sandbox and indicates potential malicious intent if used without explicit authorization. Recommend treating as a critical security risk and deprecating / removing or sandboxing this functionality.
github.com/nccgroup/singularity
v0.0.0-20261120063628-00a04fbaf541
Live on go
Blocked by Socket
High risk of data leakage and backdoor-like behavior. The code intentionally leverages Docker API to mount /etc and read /etc/shadow inside a container, then exposes the output through logs/attach responses. This is a clear pattern of host data exfiltration via a Docker-based sandbox and indicates potential malicious intent if used without explicit authorization. Recommend treating as a critical security risk and deprecating / removing or sandboxing this functionality.
github.com/ukgovernmentbeis/sandbox_escape_bench
v0.0.0-20261115144815-c07dc32601d8
Live on go
Blocked by Socket
This is an explicit container escape exploit, not ordinary application or build logic. It compiles and launches externally supplied exploit code, modifies /bin/sh, targets runc for binary overwrite, and is designed to execute a payload outside the container when subsequent docker exec operations occur. It should not be executed or included in a package.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20261120044915-f51c6aa83ed4
Live on go
Blocked by Socket
The fragment implements file I/O, but explicitly designs that I/O to evade Linux syscall-entry monitoring and discusses avoiding an environment-based detection vector. This is a significant defense-evasion indicator and warrants treating the code as high risk; no data exfiltration or other payload is visible in the supplied fragment.
github.com/W181496/MY-CTF-Challenges
v0.0.0-20231010165229-3165504af7c9
Live on go
Blocked by Socket
This module is an extremely dangerous Serializable deserialization gadget. When an attacker can cause Java deserialization to instantiate this class, its readResolve() method unconditionally spawns a bash process and base64-decodes and executes an interactive shell payload. The behavior matches malware backdoor/reverse-shell style command execution patterns and presents a critical supply-chain risk if included as a dependency.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123065341-91279bff2618
Live on go
Blocked by Socket
This is an emp3r0r command-and-control agent component, not a general-purpose utility: it fingerprints the host, can report tunnel data to its configured controller, accepts a peer instruction to terminate, and downloads and executes replacement agents. The upgrade is staged beneath RuntimeConfig.AgentRoot and launched with REPLACE_AGENT=true; the controller address and download endpoint are runtime-configured, with the comment identifying an /agent endpoint, while connectivity testing uses tun.UbuntuConnectivityURL. These are explicit remote-management and reconnaissance capabilities; checksum validation does not independently authenticate the download source. Severity is high if this code is present or run without authorization; no literal domain, IP, or credential target appears in this fragment.
github.com/W181496/MY-CTF-Challenges
v0.0.0-20231010165229-3165504af7c9
Live on go
Blocked by Socket
High-severity suspicious PHP code: it evaluates request-controlled data and uses the result to construct an outbound cURL URL, and a separate request parameter can read and disclose local file contents. It also exposes its source and includes config.php; no fixed domain, IP address, or credential target is visible. The dynamic evaluation and request-driven network behavior are strong indicators of a backdoor or unsafe concealed endpoint, though intent and the exact reachable payload depend on PHP runtime behavior and surrounding application context.
xueoj-vjtof-util
0.0.1-security
by npm
Live on npm
Blocked by Socket
Malicious code in xueoj-vjtof-util (npm) Source: amazon-inspector (6361a9939d5d4927d1ed0e68d74fc9173e377b0cd59b8734830c62e81fdb1a8e) index.js (the declared main entry) reads an undocumented _bz byte array (195 bytes beginning with the zlib magic 0x78 0x9c) from package.json, zlib-inflates it, and executes the decoded string via the Function constructor at require() time, running with full Node privileges in any process that imports the package. Execution is gated by an explicit early return when any of CI, GITHUB_ACTIONS, GITLAB_CI, TRAVIS, CIRCLECI, or SANDBOX environment variables is set, and errors are swallowed by a try/catch, so the payload fires only in developer or production environments and stays silent under common analysis contexts. Smuggling the executable blob as a numeric byte array inside package.json rather than a.js file hides it from file-level review and from scanners that only inspect JavaScript sources. The package exports nothing useful and is described generically as a 'utility', providing no legitimate reason for this pattern. Source: ghsa-malware (f33678f60adab8790527c4caf13ae874dbfc31c06492d0e96a564a8ccdeac181) 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.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123094136-63cd9914d9d0
Live on go
Blocked by Socket
This Linux-only code deliberately removes keyword-matching entries from /var/log/wtmp, /var/log/btmp, /var/log/utmp, and /var/log/auth.log or /var/log/secure, thereby enabling concealment of login or authentication activity. It also risks log loss because it replaces xtmp files before writing filtered data and can panic on a non-384-byte-aligned file. Severity is high for audit integrity; no network exfiltration or credential harvesting is present in the fragment.
github.com/jm33-m0/emp3r0r/core
v0.0.0-20250123065341-91279bff2618
Live on go
Blocked by Socket
This code is a high-confidence Spring Cloud Gateway actuator remote-code-execution exploit. It sends a crafted route containing a Runtime.exec Spring expression, refreshes the gateway configuration, and retrieves command output. It should not be used except in a tightly authorized security test environment; deploying or running it against third-party systems would be unauthorized exploitation.
hydromind
5.24.8
Live on pypi
Blocked by Socket
This module is an import-time dynamic execution wrapper that uses a native extension (`hydromind._protection_native.exec_module`) to execute `hydromind.agent` within the importer’s `globals()` context. The design is atypical for benign dependencies and is a substantial security red flag in a supply-chain context, though concrete malicious behavior (e.g., network/file/persistence/credential theft) cannot be verified without reviewing `hydromind.agent` and the native implementation.
Proactively search and detect dependencies across repositories in your organization, with actionable insights for your projects and SBOMs

Block emerging malware threats, including intentionally maintainer-added updates, along with packages that differ in name by only a few characters..
Get alerted when a dependency update introduces new risky API usage - filesystem, network, child_process, eval().
Detect obfuscated, minified, or hidden code.
Socket detects the sudden inclusion of a new maintainer, updates with telemetry or protestware added, dependencies pulled in from a remote git URL, and much more.
We help security teams work more efficiently
Get actionable alerts for the supply chain risks that matter. Socket highlights risky dependencies directly within the developer workflow.