New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

Secure OSS Dependencies

Socket for Open Source Security

Quickly evaluate the security and health of any open source package. Unlike a traditional vulnerability scanner, Socket can detect an active supply chain attack and help you block it. Socket detects over 70 issues in open source code for comprehensive protection.

Explore Integrations
Book a Demo

Call us at (844) SOCKET-0

Beyond CVE Scanning

What is Open Source Security?

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.

Install GitHub AppContact Sales
Socket Website

We protect you from vulnerable and malicious packages

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.

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/swenske/janus

v0.0.0-20261119223135-6940210c2227

Live on go

Blocked by Socket

High severity if run against systems without authorization: the code continuously generates concurrent HTTP, HTTPS, HTTP/2, and TCP traffic against hosts derived from NET, including endpoints such as /admin, /broken, /missing, and port 5432, creating denial-of-service risk. It also submits VISITOR_PASSWORD to CONTROLLER/api/auth/login and uses the resulting cookie to poll node status endpoints; the destination is environment-configured, so no fixed domain or IP is present to report. TLS certificate verification is disabled. The fragment shows no filesystem changes, code execution, or apparent credential exfiltration beyond the configured controller login.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123052205-5b62db85f75f

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.

github.com/nccgroup/singularity

v0.0.0-20261120062225-3f7e94358921

Live on go

Blocked by Socket

High severity: this is an explicit browser-based DNS-rebinding and local-network access bypass tool, not ordinary application fetch logic. It probes and navigates to a configured target, can execute WebSocket-directed fetches, and relays target response data and accessible cookies to its parent/callback or a WebSocket peer. The WebSocket endpoint is dynamically hostname-derived at ws://<server>:<configured-port>/soows (default port 3129); no fixed external domain or IP is present. The code is not substantially obfuscated, but should only be used in an authorized security-testing environment.

databag-os

0.2.0

by vinodkumarbhovi

Live on npm

Blocked by Socket

High-severity denial-of-service risk: the modified window-slide loop in module 4851's m() resets its loop counter on every iteration and hangs compression when sufficiently large input triggers window sliding (approximately 65 KB at default settings). No suspicious domains, URLs, IPs, credentials, environment-variable access, or exfiltration are present. The code otherwise implements Pako-style compression and decompression; the anomalous loop is consistent with intentional sabotage.

github.com/nccgroup/singularity

v0.0.0-20261120063628-00a04fbaf541

Live on go

Blocked by Socket

This code is an exploit/poc for Duplicati that automates detection and a sequence of privileged API calls using a harvested XSRF token from document.cookie. It is designed to manipulate backups and restores (including restoring to attacker-controlled paths) and then trigger backup runs — a workflow consistent with achieving server-side file writes and potential RCE. The snippet lacks some definitions (payloads and helpers), but intent is clearly malicious. Avoid running this code; treat as exploitation code.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123052205-5b62db85f75f

Live on go

Blocked by Socket

This fragment strongly suggests that the larger file embeds or packages a Windows credential-dumping/post-exploitation payload. It contains explicit Mimikatz references and functionality targeting browser passwords and cookies, DPAPI/master keys, LSA secrets, vaults, private keys, PowerShell credentials, and other protected secrets. No direct exfiltration endpoint is visible here, but the credential-access capability is sufficient to treat the package as unsafe and require immediate quarantine and full binary/source provenance review.

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.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20261120044915-f51c6aa83ed4

Live on go

Blocked by Socket

This code is an in-memory payload loader that can execute native PE, .NET, and script modules, including modules associated with HTTP/DNS delivery, and includes code explicitly intended to bypass AMSI, WLDP, and ETW. It can also block indefinitely or terminate its host process. These are high-risk, malware-enabling behaviors; the fragment does not show a destination domain or prove malicious intent, so severity is high but intent cannot be conclusively determined.

subscraper-extension@matias.local

1.0.17

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/yaklang/yaklang

v1.4.9-beta7.0.20261120061406-64602c49fc99

Live on go

Blocked by Socket

This module is a high-risk payload-generation utility: it compiles and runs a local Java program to generate serialized Java deserialization gadget artifacts using Shiro/ysoserial tooling. Although the shell script itself does not show explicit exfiltration or backdoor installation, it (a) executes unverified local JARs via a broad, all-jar classpath, (b) preferentially uses a potentially altered “patched” dependency if present, and (c) produces weaponizable .ser outputs. Treat the jars (including any patched variant) and Start.java/config.yaml as critical supply-chain assets requiring integrity verification.

@quandis/qbo4.messages

4.0.1-CI-20261120-091808

by eaksoy

Live on npm

Blocked by Socket

High security risk. The code implements multiple untrusted-input-to-code-execution paths: it executes server-fetched script text via inline <script> injection, evaluates template content with new Function, and inserts server-returned HTML into an editor for later rendering. It also injects/persists arbitrary CSS into the page and uses innerHTML for error rendering. If an attacker can influence any of the involved endpoints or stored templates/scripts, this can result in full DOM XSS/JavaScript execution within the origin. Immediate review should focus on strict trust controls (allowlists/signing), removing inline script/new Function, or sandboxing and sanitizing all dynamic content before execution/rendering.

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-20250123052205-5b62db85f75f

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.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This fragment is a high-visibility dynamic loader stub: it executes hydromind.mind.billing via a native extension wrapper and passes the caller’s globals(), which materially increases the potential impact of whatever code is executed. The snippet itself shows no explicit malicious behavior, but the indirection and context-passing pattern is a notable supply-chain risk indicator. Auditing hydromind.mind.billing and hydromind._protection_native for network/file/process activity, credential/secret access, persistence, and unexpected runtime side effects is necessary to confirm or rule out malicious intent.

github.com/yaklang/yaklang

v1.4.9-beta8

Live on go

Blocked by Socket

This module is a high-risk payload-generation utility: it compiles and runs a local Java program to generate serialized Java deserialization gadget artifacts using Shiro/ysoserial tooling. Although the shell script itself does not show explicit exfiltration or backdoor installation, it (a) executes unverified local JARs via a broad, all-jar classpath, (b) preferentially uses a potentially altered “patched” dependency if present, and (c) produces weaponizable .ser outputs. Treat the jars (including any patched variant) and Start.java/config.yaml as critical supply-chain assets requiring integrity verification.

github.com/jumppad-labs/jumppad

v0.5.62-0.20261119082359-299a19309985

Live on go

Blocked by Socket

This module implements a network-accessible interactive terminal using WebSockets and a PTY, spawning either a local shell or executing a shell in a specified Docker container. Untrusted query parameters select the execution target/context, and untrusted WebSocket bytes are streamed directly into the PTY stdin while PTY output is streamed back to the client. The WebSocket origin policy is permissive (accepts all origins). While this looks like application/administrative functionality rather than a stealth malware payload, it is functionally equivalent to a remote command execution/backdoor interface if any missing authentication/authorization or network exposure exists elsewhere.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This file acts as a thin import-time stager/loader: it uses a native/private exec_module helper to execute 'hydromind.research' within the current module’s globals(). That design is inherently high-risk in a software supply-chain context because it defers all real behavior to unseen modules and grants executed code broad access to the importer’s namespace. The snippet alone does not prove malware, but the pattern warrants review of hydromind._protection_native.exec_module and hydromind.research for malicious side effects (e.g., persistence, exfiltration, credential access).

github.com/nccgroup/singularity

v0.0.0-20261120063628-00a04fbaf541

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/docker/sandbox-kit-spec/v3

v3.0.0-m.13.0.20261120151750-37f283cf3547

Live on go

Blocked by Socket

This code records process arguments in a potentially world-readable file and removes/replaces /var/run/docker.sock with a server that only responds "OK", which can disrupt Docker API operations. It also changes permissions under /var/lib/docker and creates a readable marker file. These behaviors are consistent with service sabotage and possible command-line secret exposure; no outbound exfiltration or remote-control behavior is present in this fragment. Severity is high if run on a Docker host, particularly with elevated privileges.

selvoro

1.0.0

by setarekadivar1

Live on npm

Blocked by Socket

This code silently redirects visitors with a viewport narrower than 500 pixels to https://hi[.]loannvexa[.]com/m2/?utm_campaign=loannvexa_podia. This behavior is consistent with unauthorized traffic redirection and is a high-severity concern if not an intended application feature. No credential access, data exfiltration, or obfuscation is present.

github.com/developing-today/code/pkgs/identity

v0.0.0-20261120163205-96570b03c090

Live on go

Blocked by Socket

The script contains a high-risk remote code execution pattern: it retrieves an init script from a network-controlled charm endpoint, writes it to a local file, and executes it without cryptographic verification. It also transmits “keys” derived from the local charm identity material to the remote endpoint, creating a potential secret exfiltration channel. Additionally, it performs multiple supply-chain affecting operations (apt installs/upgrades, curl+dpkg installer, npm@latest install, and git clone from the internet). While the code is not obfuscated, the trust and execution flow makes it plausibly dangerous and should be treated as high risk in a supply-chain context.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123094136-63cd9914d9d0

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.

@zaiinlin/bails

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in @zaiinlin/bails (npm) Source: ghsa-malware (a97830703fca9d3f63940c57a40a1df100f7970527db082febd518e2926f3fde) 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/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.

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/swenske/janus

v0.0.0-20261119223135-6940210c2227

Live on go

Blocked by Socket

High severity if run against systems without authorization: the code continuously generates concurrent HTTP, HTTPS, HTTP/2, and TCP traffic against hosts derived from NET, including endpoints such as /admin, /broken, /missing, and port 5432, creating denial-of-service risk. It also submits VISITOR_PASSWORD to CONTROLLER/api/auth/login and uses the resulting cookie to poll node status endpoints; the destination is environment-configured, so no fixed domain or IP is present to report. TLS certificate verification is disabled. The fragment shows no filesystem changes, code execution, or apparent credential exfiltration beyond the configured controller login.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123052205-5b62db85f75f

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.

github.com/nccgroup/singularity

v0.0.0-20261120062225-3f7e94358921

Live on go

Blocked by Socket

High severity: this is an explicit browser-based DNS-rebinding and local-network access bypass tool, not ordinary application fetch logic. It probes and navigates to a configured target, can execute WebSocket-directed fetches, and relays target response data and accessible cookies to its parent/callback or a WebSocket peer. The WebSocket endpoint is dynamically hostname-derived at ws://<server>:<configured-port>/soows (default port 3129); no fixed external domain or IP is present. The code is not substantially obfuscated, but should only be used in an authorized security-testing environment.

databag-os

0.2.0

by vinodkumarbhovi

Live on npm

Blocked by Socket

High-severity denial-of-service risk: the modified window-slide loop in module 4851's m() resets its loop counter on every iteration and hangs compression when sufficiently large input triggers window sliding (approximately 65 KB at default settings). No suspicious domains, URLs, IPs, credentials, environment-variable access, or exfiltration are present. The code otherwise implements Pako-style compression and decompression; the anomalous loop is consistent with intentional sabotage.

github.com/nccgroup/singularity

v0.0.0-20261120063628-00a04fbaf541

Live on go

Blocked by Socket

This code is an exploit/poc for Duplicati that automates detection and a sequence of privileged API calls using a harvested XSRF token from document.cookie. It is designed to manipulate backups and restores (including restoring to attacker-controlled paths) and then trigger backup runs — a workflow consistent with achieving server-side file writes and potential RCE. The snippet lacks some definitions (payloads and helpers), but intent is clearly malicious. Avoid running this code; treat as exploitation code.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123052205-5b62db85f75f

Live on go

Blocked by Socket

This fragment strongly suggests that the larger file embeds or packages a Windows credential-dumping/post-exploitation payload. It contains explicit Mimikatz references and functionality targeting browser passwords and cookies, DPAPI/master keys, LSA secrets, vaults, private keys, PowerShell credentials, and other protected secrets. No direct exfiltration endpoint is visible here, but the credential-access capability is sufficient to treat the package as unsafe and require immediate quarantine and full binary/source provenance review.

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.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20261120044915-f51c6aa83ed4

Live on go

Blocked by Socket

This code is an in-memory payload loader that can execute native PE, .NET, and script modules, including modules associated with HTTP/DNS delivery, and includes code explicitly intended to bypass AMSI, WLDP, and ETW. It can also block indefinitely or terminate its host process. These are high-risk, malware-enabling behaviors; the fragment does not show a destination domain or prove malicious intent, so severity is high but intent cannot be conclusively determined.

subscraper-extension@matias.local

1.0.17

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/yaklang/yaklang

v1.4.9-beta7.0.20261120061406-64602c49fc99

Live on go

Blocked by Socket

This module is a high-risk payload-generation utility: it compiles and runs a local Java program to generate serialized Java deserialization gadget artifacts using Shiro/ysoserial tooling. Although the shell script itself does not show explicit exfiltration or backdoor installation, it (a) executes unverified local JARs via a broad, all-jar classpath, (b) preferentially uses a potentially altered “patched” dependency if present, and (c) produces weaponizable .ser outputs. Treat the jars (including any patched variant) and Start.java/config.yaml as critical supply-chain assets requiring integrity verification.

@quandis/qbo4.messages

4.0.1-CI-20261120-091808

by eaksoy

Live on npm

Blocked by Socket

High security risk. The code implements multiple untrusted-input-to-code-execution paths: it executes server-fetched script text via inline <script> injection, evaluates template content with new Function, and inserts server-returned HTML into an editor for later rendering. It also injects/persists arbitrary CSS into the page and uses innerHTML for error rendering. If an attacker can influence any of the involved endpoints or stored templates/scripts, this can result in full DOM XSS/JavaScript execution within the origin. Immediate review should focus on strict trust controls (allowlists/signing), removing inline script/new Function, or sandboxing and sanitizing all dynamic content before execution/rendering.

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-20250123052205-5b62db85f75f

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.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This fragment is a high-visibility dynamic loader stub: it executes hydromind.mind.billing via a native extension wrapper and passes the caller’s globals(), which materially increases the potential impact of whatever code is executed. The snippet itself shows no explicit malicious behavior, but the indirection and context-passing pattern is a notable supply-chain risk indicator. Auditing hydromind.mind.billing and hydromind._protection_native for network/file/process activity, credential/secret access, persistence, and unexpected runtime side effects is necessary to confirm or rule out malicious intent.

github.com/yaklang/yaklang

v1.4.9-beta8

Live on go

Blocked by Socket

This module is a high-risk payload-generation utility: it compiles and runs a local Java program to generate serialized Java deserialization gadget artifacts using Shiro/ysoserial tooling. Although the shell script itself does not show explicit exfiltration or backdoor installation, it (a) executes unverified local JARs via a broad, all-jar classpath, (b) preferentially uses a potentially altered “patched” dependency if present, and (c) produces weaponizable .ser outputs. Treat the jars (including any patched variant) and Start.java/config.yaml as critical supply-chain assets requiring integrity verification.

github.com/jumppad-labs/jumppad

v0.5.62-0.20261119082359-299a19309985

Live on go

Blocked by Socket

This module implements a network-accessible interactive terminal using WebSockets and a PTY, spawning either a local shell or executing a shell in a specified Docker container. Untrusted query parameters select the execution target/context, and untrusted WebSocket bytes are streamed directly into the PTY stdin while PTY output is streamed back to the client. The WebSocket origin policy is permissive (accepts all origins). While this looks like application/administrative functionality rather than a stealth malware payload, it is functionally equivalent to a remote command execution/backdoor interface if any missing authentication/authorization or network exposure exists elsewhere.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This file acts as a thin import-time stager/loader: it uses a native/private exec_module helper to execute 'hydromind.research' within the current module’s globals(). That design is inherently high-risk in a software supply-chain context because it defers all real behavior to unseen modules and grants executed code broad access to the importer’s namespace. The snippet alone does not prove malware, but the pattern warrants review of hydromind._protection_native.exec_module and hydromind.research for malicious side effects (e.g., persistence, exfiltration, credential access).

github.com/nccgroup/singularity

v0.0.0-20261120063628-00a04fbaf541

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/docker/sandbox-kit-spec/v3

v3.0.0-m.13.0.20261120151750-37f283cf3547

Live on go

Blocked by Socket

This code records process arguments in a potentially world-readable file and removes/replaces /var/run/docker.sock with a server that only responds "OK", which can disrupt Docker API operations. It also changes permissions under /var/lib/docker and creates a readable marker file. These behaviors are consistent with service sabotage and possible command-line secret exposure; no outbound exfiltration or remote-control behavior is present in this fragment. Severity is high if run on a Docker host, particularly with elevated privileges.

selvoro

1.0.0

by setarekadivar1

Live on npm

Blocked by Socket

This code silently redirects visitors with a viewport narrower than 500 pixels to https://hi[.]loannvexa[.]com/m2/?utm_campaign=loannvexa_podia. This behavior is consistent with unauthorized traffic redirection and is a high-severity concern if not an intended application feature. No credential access, data exfiltration, or obfuscation is present.

github.com/developing-today/code/pkgs/identity

v0.0.0-20261120163205-96570b03c090

Live on go

Blocked by Socket

The script contains a high-risk remote code execution pattern: it retrieves an init script from a network-controlled charm endpoint, writes it to a local file, and executes it without cryptographic verification. It also transmits “keys” derived from the local charm identity material to the remote endpoint, creating a potential secret exfiltration channel. Additionally, it performs multiple supply-chain affecting operations (apt installs/upgrades, curl+dpkg installer, npm@latest install, and git clone from the internet). While the code is not obfuscated, the trust and execution flow makes it plausibly dangerous and should be treated as high risk in a supply-chain context.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123094136-63cd9914d9d0

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.

@zaiinlin/bails

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in @zaiinlin/bails (npm) Source: ghsa-malware (a97830703fca9d3f63940c57a40a1df100f7970527db082febd518e2926f3fde) 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.

Get Visibility Into Open Source Dependencies with Real-Time Security Feedback

Proactively search and detect dependencies across repositories in your organization, with actionable insights for your projects and SBOMs

Organization Dashboard

Open Source Supply Chain Attack Prevention

Block Malware and Typosquatting

Block emerging malware threats, including intentionally maintainer-added updates, along with packages that differ in name by only a few characters..

Detect Privileged API Usage

Get alerted when a dependency update introduces new risky API usage - filesystem, network, child_process, eval().

Detect Hidden Code

Detect obfuscated, minified, or hidden code.

Detect Suspicious Updates

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

Cut through the noise and focus on real threats.

Get actionable alerts for the supply chain risks that matter. Socket highlights risky dependencies directly within the developer workflow.