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

v0.0.0-20141127211108-1ffe81de5ea0

Live on go

Blocked by Socket

This fragment is a staged deploy routine: it builds a local executable, forcibly disrupts existing `screen` sessions, installs the executable into a bin directory using `sudo`, and then immediately runs an external script that likely activates/configures the installed component. While actual malicious payload behavior cannot be confirmed without inspecting `tsr` and `/vagrant/tsr-screen.sh`, the combination of `killall` disruption plus privileged installation plus follow-on script execution is a strong suspicious indicator for unauthorized setup/persistence in a supply-chain/provisioning context.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20261120011131-ffcc451483dc

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.

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.

nuadg-jhtvh-util

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in nuadg-jhtvh-util (npm) Source: ghsa-malware (03b3e59ea597e144acca2700c9cee882f5b54c4c62556b232129c1c3ab641068) 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/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The code is intentionally malicious exploit tooling. It uses container mount metadata to locate a host-backed file, replaces /etc/hosts with an executable payload, and arranges for /flag.txt to be copied into the host-side file. This indicates attempted container escape, privilege escalation, or secret exfiltration. The script should not be executed.

subscraper-extension@matias.local

1.0.15

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/nccgroup/singularity

v0.0.0-20261120062225-3f7e94358921

Live on go

Blocked by Socket

This code exhibits clear malicious intent: it probes for the AWS instance metadata service and contains a hardcoded external endpoint to which supplied data (body) is sent. It also logs sensitive inputs to console and registers itself in a registry for later invocation. Treat this code as a backdoor/data‑exfiltration component. Remove immediately, audit repository for other instances or callers that may supply credentials/metadata to attack(), and assume compromise of any secrets that may have been exposed.

github.com/utisss/utctf-2022

v0.0.0-20220315173045-79601865b2af

Live on go

Blocked by Socket

This code is a high-confidence malicious payload generator. It constructs a steganographically encoded PNG containing an obfuscated JavaScript `fetch` call that exfiltrates `document.cookie` to a hardcoded attacker-controlled HTTP endpoint. The use of structured constants/offset writing and XOR encoding strongly indicates deliberate exploit/payload engineering rather than benign image manipulation. Use of the generated output in any browser or processing pipeline that triggers/decodes the embedded script would present an extreme risk of session/cookie theft.

imango@mgtv.com

1.2.3

by anonymous-8d38748f7f539c10ff287c600dc66aa5

Live on firefox

Blocked by Socket

This fragment implements extension analytics that transmit visited tab URLs, persistent device identifiers, and available user/account and browser metadata to https://pcweb-v1.log.mgtv.com/dispatcher.do; it also sends native SDK response data. This is a significant privacy concern for a new-tab extension because navigation reporting covers ordinary browsing activity and is not necessary for displaying a new-tab page. The fragment also fetches caller-supplied URLs for metadata extraction, but shows no execution of fetched content, cookie theft, or credential capture. Severity: high privacy risk; no clear malware behavior beyond invasive tracking is established by this fragment.

github.com/nccgroup/singularity

v0.0.0-20261120063628-00a04fbaf541

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.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This file is a high-suspicion import-time execution trampoline: it uses a native extension wrapper to dynamically execute the module 'hydromind.model.telemetry' with full access to the caller’s globals() and contextual __file__. While no explicit malicious operations are visible in the fragment, the delegation to unseen native code plus a dynamically executed 'telemetry' module makes supply-chain risk non-trivial and warrants direct review of hydromind._protection_native and hydromind.model.telemetry for tracking, data collection, exfiltration, or hidden backdoor behavior.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123065341-91279bff2618

Live on go

Blocked by Socket

This code is a command-and-control agent handler that accepts remote commands, executes arbitrary programs, transfers files, gathers system information, and modifies or deletes local files and processes. These capabilities can enable unauthorized control and data theft; the fragment does not establish whether its deployment is authorized, and contains no hardcoded network indicators or credentials. Severity is high if deployed without authorization.

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/jm33-m0/emp3r0r/core

v0.0.0-20261120044915-f51c6aa83ed4

Live on go

Blocked by Socket

High severity: this fragment implements C2-agent primitives for executing BOF-supplied commands, reading and writing files, uploading file contents, and relaying socket traffic through a configured C2 proxy. These capabilities can enable unauthorized remote control if deployed without authorization, although this fragment alone does not establish how the surrounding agent is installed or used. No specific domain, URL, IP address, credential target, or environment-variable harvesting is shown; the code is not materially obfuscated.

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.

@kingorwot/my-baileys

1.0.0

by kingorwot

Live on npm

Blocked by Socket

The module retrieves a remote list controlled by an attacker after a delay and causes the authenticated user account to follow each listed item on the target platform, enabling automated account-state manipulation without local data exfiltration or command execution.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The code is clearly malicious in behavior: it exploits access to kernel-module loading to execute a command on the host and exfiltrate /flag.txt through a shared directory. It requires favorable host configuration such as CAP_SYS_MODULE, kernel headers, and access to the host kernel, but where those conditions exist it can compromise host integrity and confidentiality. The package or script should not be executed.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The script is an explicit container-escape and command-injection exploit. It executes an externally supplied Python payload, identifies the host gateway, targets a diagnostic endpoint, and attempts to exfiltrate `/flag.txt`. It should not be run in an untrusted environment or included in a package.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

This is an intentional privileged-container escape and host data-exfiltration script, not normal application functionality. It should not be executed in an untrusted environment. The code is readable and not meaningfully obfuscated.

smfos-bskdz-util

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in smfos-bskdz-util (npm) Source: amazon-inspector (ec58aa63a556255a6052491e8d50ff5f9e44d58f32044028f3f1ae978789e0c0) On require, index.js reads a numeric byte array from a non-standard `_b` field in package.json, XORs each byte with 0x96, and passes the result to the Function constructor along with `require` and `__dirname`. In version 1.0.1 the decoded bytes resolve to a trivial `console.log(1)`, but the package exports an empty object and advertises itself as a utility, so the only functional behavior shipped is this dynamic-execution channel. The payload is stored in a manifest field under a single-letter key, outside any shipped.js source, and is only reachable through the XOR transform — a deliberate obfuscation shape that lets any future published version execute arbitrary author-controlled code at import time with full access to `require` and the installing project's directory. Source: ghsa-malware (f15455f24cd57ac6b7bdd0de11c511ba1ce862fd870c2bdad19f93f67cc34b45) 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/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

This is an intentionally offensive container-escape launcher. Although it may be appropriate in a controlled security challenge or authorized exploit test, running it against a real environment poses a critical security risk because it compiles untrusted native code and attempts to exploit a kernel vulnerability to access /flag.txt.

github.com/nccgroup/singularity

v0.0.0-20261120062225-3f7e94358921

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/wenathlan/devthink/devthink/v2

v2.0.187-0.20261120003855-598c13896645

Live on go

Blocked by Socket

High-severity credential-capture behavior: this code obtains or reuses a GitHub OAuth token with `repo`, `workflow`, and `read:org` scopes, stores it in local credential files, configures Git to use stored credentials, and initiates repository synchronization. Relevant destinations include `github[.]com`, `api[.]github[.]com`, and the referenced repository `github[.]com/wenathlan/devthink[.]git`; relevant files include `.github-token`, `.git-credentials`, `.git-credentials.bak`, and `.polar-auth.json`. The available fragment is truncated inside `synchead`, but the token acquisition and persistence are explicit; treat as dangerous.

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.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This module is a thin, import-time bootstrapper that delegates execution to a native helper to load and run `hydromind.mind.shared` inside the current module’s `globals()` namespace. The actual security-relevant behavior is hidden in `hydromind.mind.shared` and/or the compiled `_protection_native.exec_module`, which makes supply-chain auditing difficult. No explicit malicious indicators (network/files/credentials/process execution) are present in this fragment alone, but the dynamic native execution pattern is a meaningful security risk that warrants direct review of the delegated module and native helper implementation.

github.com/tsuru/tsuru

v0.0.0-20141127211108-1ffe81de5ea0

Live on go

Blocked by Socket

This fragment is a staged deploy routine: it builds a local executable, forcibly disrupts existing `screen` sessions, installs the executable into a bin directory using `sudo`, and then immediately runs an external script that likely activates/configures the installed component. While actual malicious payload behavior cannot be confirmed without inspecting `tsr` and `/vagrant/tsr-screen.sh`, the combination of `killall` disruption plus privileged installation plus follow-on script execution is a strong suspicious indicator for unauthorized setup/persistence in a supply-chain/provisioning context.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20261120011131-ffcc451483dc

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.

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.

nuadg-jhtvh-util

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in nuadg-jhtvh-util (npm) Source: ghsa-malware (03b3e59ea597e144acca2700c9cee882f5b54c4c62556b232129c1c3ab641068) 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/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The code is intentionally malicious exploit tooling. It uses container mount metadata to locate a host-backed file, replaces /etc/hosts with an executable payload, and arranges for /flag.txt to be copied into the host-side file. This indicates attempted container escape, privilege escalation, or secret exfiltration. The script should not be executed.

subscraper-extension@matias.local

1.0.15

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/nccgroup/singularity

v0.0.0-20261120062225-3f7e94358921

Live on go

Blocked by Socket

This code exhibits clear malicious intent: it probes for the AWS instance metadata service and contains a hardcoded external endpoint to which supplied data (body) is sent. It also logs sensitive inputs to console and registers itself in a registry for later invocation. Treat this code as a backdoor/data‑exfiltration component. Remove immediately, audit repository for other instances or callers that may supply credentials/metadata to attack(), and assume compromise of any secrets that may have been exposed.

github.com/utisss/utctf-2022

v0.0.0-20220315173045-79601865b2af

Live on go

Blocked by Socket

This code is a high-confidence malicious payload generator. It constructs a steganographically encoded PNG containing an obfuscated JavaScript `fetch` call that exfiltrates `document.cookie` to a hardcoded attacker-controlled HTTP endpoint. The use of structured constants/offset writing and XOR encoding strongly indicates deliberate exploit/payload engineering rather than benign image manipulation. Use of the generated output in any browser or processing pipeline that triggers/decodes the embedded script would present an extreme risk of session/cookie theft.

imango@mgtv.com

1.2.3

by anonymous-8d38748f7f539c10ff287c600dc66aa5

Live on firefox

Blocked by Socket

This fragment implements extension analytics that transmit visited tab URLs, persistent device identifiers, and available user/account and browser metadata to https://pcweb-v1.log.mgtv.com/dispatcher.do; it also sends native SDK response data. This is a significant privacy concern for a new-tab extension because navigation reporting covers ordinary browsing activity and is not necessary for displaying a new-tab page. The fragment also fetches caller-supplied URLs for metadata extraction, but shows no execution of fetched content, cookie theft, or credential capture. Severity: high privacy risk; no clear malware behavior beyond invasive tracking is established by this fragment.

github.com/nccgroup/singularity

v0.0.0-20261120063628-00a04fbaf541

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.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This file is a high-suspicion import-time execution trampoline: it uses a native extension wrapper to dynamically execute the module 'hydromind.model.telemetry' with full access to the caller’s globals() and contextual __file__. While no explicit malicious operations are visible in the fragment, the delegation to unseen native code plus a dynamically executed 'telemetry' module makes supply-chain risk non-trivial and warrants direct review of hydromind._protection_native and hydromind.model.telemetry for tracking, data collection, exfiltration, or hidden backdoor behavior.

github.com/jm33-m0/emp3r0r/core

v0.0.0-20250123065341-91279bff2618

Live on go

Blocked by Socket

This code is a command-and-control agent handler that accepts remote commands, executes arbitrary programs, transfers files, gathers system information, and modifies or deletes local files and processes. These capabilities can enable unauthorized control and data theft; the fragment does not establish whether its deployment is authorized, and contains no hardcoded network indicators or credentials. Severity is high if deployed without authorization.

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/jm33-m0/emp3r0r/core

v0.0.0-20261120044915-f51c6aa83ed4

Live on go

Blocked by Socket

High severity: this fragment implements C2-agent primitives for executing BOF-supplied commands, reading and writing files, uploading file contents, and relaying socket traffic through a configured C2 proxy. These capabilities can enable unauthorized remote control if deployed without authorization, although this fragment alone does not establish how the surrounding agent is installed or used. No specific domain, URL, IP address, credential target, or environment-variable harvesting is shown; the code is not materially obfuscated.

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.

@kingorwot/my-baileys

1.0.0

by kingorwot

Live on npm

Blocked by Socket

The module retrieves a remote list controlled by an attacker after a delay and causes the authenticated user account to follow each listed item on the target platform, enabling automated account-state manipulation without local data exfiltration or command execution.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The code is clearly malicious in behavior: it exploits access to kernel-module loading to execute a command on the host and exfiltrate /flag.txt through a shared directory. It requires favorable host configuration such as CAP_SYS_MODULE, kernel headers, and access to the host kernel, but where those conditions exist it can compromise host integrity and confidentiality. The package or script should not be executed.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The script is an explicit container-escape and command-injection exploit. It executes an externally supplied Python payload, identifies the host gateway, targets a diagnostic endpoint, and attempts to exfiltrate `/flag.txt`. It should not be run in an untrusted environment or included in a package.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

This is an intentional privileged-container escape and host data-exfiltration script, not normal application functionality. It should not be executed in an untrusted environment. The code is readable and not meaningfully obfuscated.

smfos-bskdz-util

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in smfos-bskdz-util (npm) Source: amazon-inspector (ec58aa63a556255a6052491e8d50ff5f9e44d58f32044028f3f1ae978789e0c0) On require, index.js reads a numeric byte array from a non-standard `_b` field in package.json, XORs each byte with 0x96, and passes the result to the Function constructor along with `require` and `__dirname`. In version 1.0.1 the decoded bytes resolve to a trivial `console.log(1)`, but the package exports an empty object and advertises itself as a utility, so the only functional behavior shipped is this dynamic-execution channel. The payload is stored in a manifest field under a single-letter key, outside any shipped.js source, and is only reachable through the XOR transform — a deliberate obfuscation shape that lets any future published version execute arbitrary author-controlled code at import time with full access to `require` and the installing project's directory. Source: ghsa-malware (f15455f24cd57ac6b7bdd0de11c511ba1ce862fd870c2bdad19f93f67cc34b45) 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/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

This is an intentionally offensive container-escape launcher. Although it may be appropriate in a controlled security challenge or authorized exploit test, running it against a real environment poses a critical security risk because it compiles untrusted native code and attempts to exploit a kernel vulnerability to access /flag.txt.

github.com/nccgroup/singularity

v0.0.0-20261120062225-3f7e94358921

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/wenathlan/devthink/devthink/v2

v2.0.187-0.20261120003855-598c13896645

Live on go

Blocked by Socket

High-severity credential-capture behavior: this code obtains or reuses a GitHub OAuth token with `repo`, `workflow`, and `read:org` scopes, stores it in local credential files, configures Git to use stored credentials, and initiates repository synchronization. Relevant destinations include `github[.]com`, `api[.]github[.]com`, and the referenced repository `github[.]com/wenathlan/devthink[.]git`; relevant files include `.github-token`, `.git-credentials`, `.git-credentials.bak`, and `.polar-auth.json`. The available fragment is truncated inside `synchead`, but the token acquisition and persistence are explicit; treat as dangerous.

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.

hydromind

5.24.8

Live on pypi

Blocked by Socket

This module is a thin, import-time bootstrapper that delegates execution to a native helper to load and run `hydromind.mind.shared` inside the current module’s `globals()` namespace. The actual security-relevant behavior is hidden in `hydromind.mind.shared` and/or the compiled `_protection_native.exec_module`, which makes supply-chain auditing difficult. No explicit malicious indicators (network/files/credentials/process execution) are present in this fragment alone, but the dynamic native execution pattern is a meaningful security risk that warrants direct review of the delegated module and native helper implementation.

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.