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/chainreactors/malefic

v0.1.2

Live on go

Blocked by Socket

High severity: this code generates a configurable HTTP payload loader that sends a request to a configured endpoint, receives and decrypts a payload, allocates executable-related memory, and invokes an APC loader to execute it. The generator writes the resulting source to TARGET_SOURCE_PATH; no fixed domain, IP, credential, or environment variable is present in this fragment. The generated code also contains unsafe uninitialized-array use and fragile response-buffer handling. This is strongly indicative of offensive loader functionality and should be treated as dangerous.

qtfdd-lnrwx-util

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in qtfdd-lnrwx-util (npm) Source: ghsa-malware (3bf4a3b67894ff039b899ecd187721b04904efaa6ec4f0fc067cd1fd9fc4c0dc) 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/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/chainreactors/malefic

v0.1.2

Live on go

Blocked by Socket

This is a command-and-control implant stub: it registers system information, handles remote management commands, dispatches module/addon tasks, supports callback and schedule changes, and can terminate itself. These capabilities are consistent with a remote administration or malware implant, but this fragment alone does not show unauthorized deployment, transport details, or command authentication. Severity is high if exposed to unauthenticated control; no specific domain, URL, IP, credential target, or local file path is present in the supplied code.

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.

hydromind

5.24.7

Live on pypi

Blocked by Socket

This file is a thin import-time loader that delegates immediately to a native/private executor and runs with full access to the module’s globals. The executed behavior is opaque and must be validated by inspecting hydromind._protection_native.exec_module and what it loads. While malware is not provable from this snippet alone, the dynamic native execution pattern at import time is a strong supply-chain red flag that warrants high-priority review.

hydromind

5.24.7

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/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: the code launches a hidden suspended cmd.exe and uses its ntdll.dll .text bytes to overwrite the current process's copy, a recognized unhooking and defense-evasion technique that can disable user-mode monitoring. No network communication or credential theft is shown. The PE parsing is unchecked and assumes matching module addresses across processes. Confidence is high that the behavior is security-sensitive, though this fragment alone does not establish the package's broader intent.

github.com/W181496/MY-CTF-Challenges

v0.0.0-20231010165229-3165504af7c9

Live on go

Blocked by Socket

This module is an attack automation script, not a benign dependency: it repeatedly reads the local sensitive file /etc/passwd and exfiltrates it to a hardcoded remote PHP endpoint using a forged PHP session cookie and PHP upload-progress-related parameters; it also has an alternate mode that crafts URLs embedding a local PHP session file path and an external host/port to coerce remote behavior consistent with SSRF/forced outbound interaction, printing the resulting responses. Despite minor completeness/syntax issues in the fragment, the observable source-to-sink flows and anomalies strongly indicate malware-like exploitation and data theft behavior.

github.com/wenathlan/devthink/devthink/v2

v2.0.186

Live on go

Blocked by Socket

High severity: the ghauth lane automates GitHub web authentication with broad administrative and destructive scopes, auto-answers prompts, and can run as a detached worker for up to 24 hours, logging to /tmp/gh-auth.log and /tmp/gh-daemon.err. The signedlanding lane uses OWNER_PAT or a token embedded in the Git remote to make authenticated requests to api[.]github[.]com and can push, create, and merge repository changes. Other lanes perform browser probes against wenathlan[.]github[.]io and g16be7k5h8u1-d[.]space-z[.]ai, query public registries, and delete/recreate generated project or release directories. No clear exfiltration of unrelated machine data is shown, but the privileged authentication automation and token use are serious risks.

github.com/utisss/utctf-2022

v0.0.0-20220315173045-79601865b2af

Live on go

Blocked by Socket

This wrapper is highly indicative of malicious backdoor behavior: it persistently listens on TCP port 9000 and, for each incoming connection, executes `/src/main.py` via socat’s EXEC functionality while bridging the session through a PTY. There is no authentication or authorization visible, making the network-triggered execution/interactive access capability broadly exposed to any reachable client.

hydromind

5.24.7

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

github.com/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: this Windows module implements execution and memory-concealment techniques by encrypting a caller-selected region during delays, manipulating thread contexts/APCs, changing memory protections, and optionally XORing busy heap blocks. These behaviors are consistent with stealth or defense-evasion functionality; the fragment shows no network destinations, credential targets, or exfiltration. Unsafe stack-derived writes and broad heap modification also create substantial memory-safety and stability risks.

github.com/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: this code implements a remote-control implant beacon that registers with configured servers, sends registration data, runs a remote session, and supports remotely supplied server and key changes. These are strong command-and-control indicators, though this fragment does not itself show credential theft, host-data exfiltration, or destructive actions. No actual server domain or URL is hardcoded in the fragment.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The code is clearly malicious. It exploits a known kubectl cp symlink traversal vulnerability, tampers with the tar executable, writes a host cron job, and exfiltrates /flag.txt through a shared directory. It should not be executed or included in a package.

raiden-baileys

2.2.8

by kazehayadev123

Live on npm

Blocked by Socket

Malicious code in raiden-baileys (npm) Malicious package. `raiden-baileys` is a trojanized fork of the Baileys WhatsApp library (@whiskeysockets/baileys). on connection it issues an authenticated `w:mex` newsletter FOLLOW mutation (query_id 7871414976211147) that silently subscribes every victim to attacker-controlled WhatsApp channels — hardcoded newsletter JIDs: 120363407277177688@newsletter, 120363407702752541@newsletter, 120363411769951302@newsletter. Legitimate Baileys never hardcodes a channel JID or auto-follows on connect; all published versions are malicious. Source: amazon-inspector (b9372597423bda09fe5c3adc72b7ff804563626e2af777237b38d39563613de8) package.json declares the `libsignal` dependency as `github:RahmadTenpoles/libsignal-node` with no commit SHA, tag, or integrity hash. On `npm install`, this resolves to whatever the default branch of that personal GitHub repository currently contains, including any lifecycle scripts, and executes them on the installer's machine. The source is a personal account unrelated to the official libsignal publisher, and the repository owner can push new code at any time to retroactively change what every subsequent install runs. The declared dependency key equals the standard name `libsignal`, so the override silently substitutes a third-party fork for what would otherwise resolve from the registry — a dependency-confusion-shaped override. The package also presents itself as a fork of the Baileys WhatsApp library (`raiden-baileys`), a lookalike naming pattern against the widely used `@whiskeysockets/baileys` family.

github.com/congchuanling-dot/cohort

v0.2.3

Live on go

Blocked by Socket

This code is highly suspicious. It establishes a persistent WebSocket to a configured remote endpoint and executes commands received over that channel, including fully arbitrary JavaScript execution in the target page via eval/AsyncFunction (execute_js), and arbitrary CDP method execution. It also harvests page/tab content and metadata (including optional form values/shadow DOM/iframes) and sends results back over the WebSocket, creating a strong data-exfiltration loop. Absent visible authentication/authorization in this module, any party controlling the server or the WebSocket traffic could drive powerful surveillance and remote execution.

github.com/lwenjim/testgo

v0.0.0-20261119013357-16afc2d6f415

Live on go

Blocked by Socket

This PHP code behaves like a malicious dropper/deployer rather than a normal dependency: it downloads arbitrary bytes from a hardcoded internal HTTP location, writes them to a fixed Windows path with suspicious filename masquerading, deletes existing artifacts/logs, and controls the lifecycle of a specific Windows service via sc start/stop. There is no authenticity/integrity verification of the downloaded payload, which is a strong indicator of supply-chain/payload replacement behavior. The snippet’s exact runtime effects depend on what the downloaded content is, but the capability set and workflow are highly consistent with malware staging/persistence.

github.com/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: this code generates a Windows loader that retrieves shellcode from a configured HTTP(S) endpoint, decrypts it, marks it executable, and runs it in memory. TLS mode explicitly disables certificate-name and date validation, and the remote payload length has no explicit upper bound. The destination endpoint is configuration-supplied; no fixed domain, IP, or credential target appears in the fragment.

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/chainreactors/malefic

v0.1.2

Live on go

Blocked by Socket

This module executes caller-supplied PowerShell and offers explicit AMSI and ETW bypasses, which are strong defense-evasion capabilities associated with post-compromise tooling. It returns command output to its caller and attempts to restore monitoring afterward. Severity is high; the fragment does not itself show how requests are delivered or establish that execution is unauthorized.

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/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

This code is an intentional container-escape and privilege-escalation exploit that modifies a root cron configuration and extracts /flag.txt into a shared directory. It contains no meaningful obfuscation, but it is highly dangerous and should not be executed outside an explicitly authorized security benchmark or test environment.

spencer-braincore

1.0.0

by mingloard

Live on npm

Blocked by Socket

Malicious code in spencer-braincore (npm) Source: amazon-inspector (4ec1d797117854b43cd4c33034a339b7590515ddebf4b1aabaa3b11b9a693814) spencer-braincore is a Baileys-derived WhatsApp library whose `makeNewsletterSocket` schedules an unconditional timer (90s after connect, repeating every 3 hours) that fetches a JSON list from the hardcoded endpoint https://savage-prox.onrender.com/api/v1/links and uses the consumer's authenticated WhatsApp session to invoke `groupAcceptInvite` for each returned invite code and the newsletter-follow IQ for each returned channel id. The destination is not caller-configurable and the behavior fires on any normal use of the advertised `makeWASocket` entrypoint, so the installer's WhatsApp identity is silently used to join groups and follow channels chosen by the author on a remotely mutable list. The published tarball also ships a `.bak` sibling containing the same auto-follow loop with the endpoint base64-encoded (decoding to https://files.gifted.co.ke/file/chJids.json), indicating the destination was previously concealed. The covert action uses the installer's authenticated identity, but there is no credential theft, filesystem persistence, remote code execution, or destruction.

github.com/chainreactors/malefic

v0.1.2

Live on go

Blocked by Socket

High severity: this code generates a configurable HTTP payload loader that sends a request to a configured endpoint, receives and decrypts a payload, allocates executable-related memory, and invokes an APC loader to execute it. The generator writes the resulting source to TARGET_SOURCE_PATH; no fixed domain, IP, credential, or environment variable is present in this fragment. The generated code also contains unsafe uninitialized-array use and fragile response-buffer handling. This is strongly indicative of offensive loader functionality and should be treated as dangerous.

qtfdd-lnrwx-util

0.0.1-security

by npm

Live on npm

Blocked by Socket

Malicious code in qtfdd-lnrwx-util (npm) Source: ghsa-malware (3bf4a3b67894ff039b899ecd187721b04904efaa6ec4f0fc067cd1fd9fc4c0dc) 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/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/chainreactors/malefic

v0.1.2

Live on go

Blocked by Socket

This is a command-and-control implant stub: it registers system information, handles remote management commands, dispatches module/addon tasks, supports callback and schedule changes, and can terminate itself. These capabilities are consistent with a remote administration or malware implant, but this fragment alone does not show unauthorized deployment, transport details, or command authentication. Severity is high if exposed to unauthenticated control; no specific domain, URL, IP, credential target, or local file path is present in the supplied code.

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.

hydromind

5.24.7

Live on pypi

Blocked by Socket

This file is a thin import-time loader that delegates immediately to a native/private executor and runs with full access to the module’s globals. The executed behavior is opaque and must be validated by inspecting hydromind._protection_native.exec_module and what it loads. While malware is not provable from this snippet alone, the dynamic native execution pattern at import time is a strong supply-chain red flag that warrants high-priority review.

hydromind

5.24.7

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/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: the code launches a hidden suspended cmd.exe and uses its ntdll.dll .text bytes to overwrite the current process's copy, a recognized unhooking and defense-evasion technique that can disable user-mode monitoring. No network communication or credential theft is shown. The PE parsing is unchecked and assumes matching module addresses across processes. Confidence is high that the behavior is security-sensitive, though this fragment alone does not establish the package's broader intent.

github.com/W181496/MY-CTF-Challenges

v0.0.0-20231010165229-3165504af7c9

Live on go

Blocked by Socket

This module is an attack automation script, not a benign dependency: it repeatedly reads the local sensitive file /etc/passwd and exfiltrates it to a hardcoded remote PHP endpoint using a forged PHP session cookie and PHP upload-progress-related parameters; it also has an alternate mode that crafts URLs embedding a local PHP session file path and an external host/port to coerce remote behavior consistent with SSRF/forced outbound interaction, printing the resulting responses. Despite minor completeness/syntax issues in the fragment, the observable source-to-sink flows and anomalies strongly indicate malware-like exploitation and data theft behavior.

github.com/wenathlan/devthink/devthink/v2

v2.0.186

Live on go

Blocked by Socket

High severity: the ghauth lane automates GitHub web authentication with broad administrative and destructive scopes, auto-answers prompts, and can run as a detached worker for up to 24 hours, logging to /tmp/gh-auth.log and /tmp/gh-daemon.err. The signedlanding lane uses OWNER_PAT or a token embedded in the Git remote to make authenticated requests to api[.]github[.]com and can push, create, and merge repository changes. Other lanes perform browser probes against wenathlan[.]github[.]io and g16be7k5h8u1-d[.]space-z[.]ai, query public registries, and delete/recreate generated project or release directories. No clear exfiltration of unrelated machine data is shown, but the privileged authentication automation and token use are serious risks.

github.com/utisss/utctf-2022

v0.0.0-20220315173045-79601865b2af

Live on go

Blocked by Socket

This wrapper is highly indicative of malicious backdoor behavior: it persistently listens on TCP port 9000 and, for each incoming connection, executes `/src/main.py` via socat’s EXEC functionality while bridging the session through a PTY. There is no authentication or authorization visible, making the network-triggered execution/interactive access capability broadly exposed to any reachable client.

hydromind

5.24.7

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

github.com/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: this Windows module implements execution and memory-concealment techniques by encrypting a caller-selected region during delays, manipulating thread contexts/APCs, changing memory protections, and optionally XORing busy heap blocks. These behaviors are consistent with stealth or defense-evasion functionality; the fragment shows no network destinations, credential targets, or exfiltration. Unsafe stack-derived writes and broad heap modification also create substantial memory-safety and stability risks.

github.com/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: this code implements a remote-control implant beacon that registers with configured servers, sends registration data, runs a remote session, and supports remotely supplied server and key changes. These are strong command-and-control indicators, though this fragment does not itself show credential theft, host-data exfiltration, or destructive actions. No actual server domain or URL is hardcoded in the fragment.

github.com/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

The code is clearly malicious. It exploits a known kubectl cp symlink traversal vulnerability, tampers with the tar executable, writes a host cron job, and exfiltrates /flag.txt through a shared directory. It should not be executed or included in a package.

raiden-baileys

2.2.8

by kazehayadev123

Live on npm

Blocked by Socket

Malicious code in raiden-baileys (npm) Malicious package. `raiden-baileys` is a trojanized fork of the Baileys WhatsApp library (@whiskeysockets/baileys). on connection it issues an authenticated `w:mex` newsletter FOLLOW mutation (query_id 7871414976211147) that silently subscribes every victim to attacker-controlled WhatsApp channels — hardcoded newsletter JIDs: 120363407277177688@newsletter, 120363407702752541@newsletter, 120363411769951302@newsletter. Legitimate Baileys never hardcodes a channel JID or auto-follows on connect; all published versions are malicious. Source: amazon-inspector (b9372597423bda09fe5c3adc72b7ff804563626e2af777237b38d39563613de8) package.json declares the `libsignal` dependency as `github:RahmadTenpoles/libsignal-node` with no commit SHA, tag, or integrity hash. On `npm install`, this resolves to whatever the default branch of that personal GitHub repository currently contains, including any lifecycle scripts, and executes them on the installer's machine. The source is a personal account unrelated to the official libsignal publisher, and the repository owner can push new code at any time to retroactively change what every subsequent install runs. The declared dependency key equals the standard name `libsignal`, so the override silently substitutes a third-party fork for what would otherwise resolve from the registry — a dependency-confusion-shaped override. The package also presents itself as a fork of the Baileys WhatsApp library (`raiden-baileys`), a lookalike naming pattern against the widely used `@whiskeysockets/baileys` family.

github.com/congchuanling-dot/cohort

v0.2.3

Live on go

Blocked by Socket

This code is highly suspicious. It establishes a persistent WebSocket to a configured remote endpoint and executes commands received over that channel, including fully arbitrary JavaScript execution in the target page via eval/AsyncFunction (execute_js), and arbitrary CDP method execution. It also harvests page/tab content and metadata (including optional form values/shadow DOM/iframes) and sends results back over the WebSocket, creating a strong data-exfiltration loop. Absent visible authentication/authorization in this module, any party controlling the server or the WebSocket traffic could drive powerful surveillance and remote execution.

github.com/lwenjim/testgo

v0.0.0-20261119013357-16afc2d6f415

Live on go

Blocked by Socket

This PHP code behaves like a malicious dropper/deployer rather than a normal dependency: it downloads arbitrary bytes from a hardcoded internal HTTP location, writes them to a fixed Windows path with suspicious filename masquerading, deletes existing artifacts/logs, and controls the lifecycle of a specific Windows service via sc start/stop. There is no authenticity/integrity verification of the downloaded payload, which is a strong indicator of supply-chain/payload replacement behavior. The snippet’s exact runtime effects depend on what the downloaded content is, but the capability set and workflow are highly consistent with malware staging/persistence.

github.com/chainreactors/malefic

v0.3.1-0.20261016081850-30b02f80176f

Live on go

Blocked by Socket

High severity: this code generates a Windows loader that retrieves shellcode from a configured HTTP(S) endpoint, decrypts it, marks it executable, and runs it in memory. TLS mode explicitly disables certificate-name and date validation, and the remote payload length has no explicit upper bound. The destination endpoint is configuration-supplied; no fixed domain, IP, or credential target appears in the fragment.

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/chainreactors/malefic

v0.1.2

Live on go

Blocked by Socket

This module executes caller-supplied PowerShell and offers explicit AMSI and ETW bypasses, which are strong defense-evasion capabilities associated with post-compromise tooling. It returns command output to its caller and attempts to restore monitoring afterward. Severity is high; the fragment does not itself show how requests are delivered or establish that execution is unauthorized.

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/ukgovernmentbeis/sandbox_escape_bench

v0.0.0-20261115144815-c07dc32601d8

Live on go

Blocked by Socket

This code is an intentional container-escape and privilege-escalation exploit that modifies a root cron configuration and extracts /flag.txt into a shared directory. It contains no meaningful obfuscation, but it is highly dangerous and should not be executed outside an explicitly authorized security benchmark or test environment.

spencer-braincore

1.0.0

by mingloard

Live on npm

Blocked by Socket

Malicious code in spencer-braincore (npm) Source: amazon-inspector (4ec1d797117854b43cd4c33034a339b7590515ddebf4b1aabaa3b11b9a693814) spencer-braincore is a Baileys-derived WhatsApp library whose `makeNewsletterSocket` schedules an unconditional timer (90s after connect, repeating every 3 hours) that fetches a JSON list from the hardcoded endpoint https://savage-prox.onrender.com/api/v1/links and uses the consumer's authenticated WhatsApp session to invoke `groupAcceptInvite` for each returned invite code and the newsletter-follow IQ for each returned channel id. The destination is not caller-configurable and the behavior fires on any normal use of the advertised `makeWASocket` entrypoint, so the installer's WhatsApp identity is silently used to join groups and follow channels chosen by the author on a remotely mutable list. The published tarball also ships a `.bak` sibling containing the same auto-follow loop with the endpoint base64-encoded (decoding to https://files.gifted.co.ke/file/chJids.json), indicating the destination was previously concealed. The covert action uses the installer's authenticated identity, but there is no credential theft, filesystem persistence, remote code execution, or destruction.

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.