Secure your dependencies. Ship with confidence.

The code operates as a Google Ads API integration wrapper, reading user input, constructing a GAQL-like query, and issuing a POST request to fetch user lists. While it does not demonstrate explicit malware, the combination of heavy obfuscation, dynamic string assembly, and potential injection surface from user-derived inputs requires careful audit of input validation, escaping for GAQL, and credential handling. The behavior warrants remediation to ensure robust input sanitization, removal of unnecessary obfuscation, and explicit error handling to avoid silent failures and potential data leakage.

This postinstall hook executes local code that, per the package metadata, is intended to encode and exfiltrate data to GitHub. Treat this as malicious: do not install or run without fully auditing index.js in a safe environment. There is a high risk of data exfiltration and other malicious activity.

This package will execute its bundled index.js during installation. Given the package name and description explicitly describing backdoor/persistence behavior, treat this as malicious. Do not install. Inspect the contents of index.js in a safe environment (offline/sandbox) if analysis is required, and if this was installed on production/self-hosted CI, assume compromise and perform incident response (rotate credentials, rebuild runners, check for persistence mechanisms and network egress).

The code appears to be a legitimate part of the SpiderMesh library, but it has potential security risks and unusual patterns that should be further reviewed and analyzed.

The code is designed to fetch and execute external payloads with minimal validation, enabling serious supply-chain and remote code execution risks. It lacks integrity checks (signatures, checksums), authentication, and robust error handling. The gunzip handling also appears flawed, which could cause runtime issues. The overall security risk is high for untrusted sources, and the malware likelihood is non-zero given the ability to run arbitrary downloaded code.

The code is performing actions consistent with malicious behavior by collecting and transmitting sensitive system information to an external server without user consent. This poses a significant security risk.

Live on pypi for 18 hours and 12 minutes before removal. Socket users were protected even while the package was live.

This script downloads a file from a remote server using curl. The URL contains a variable that is not defined in the script, which could indicate a typo or a malicious attempt to execute arbitrary code. The contents of the downloaded file should be reviewed for safety.

Live on npm for 9 hours and 32 minutes before removal. Socket users were protected even while the package was live.

The module contains high-risk operations: executing arbitrary shell commands via subprocess with shell=True and writing/appending to files without validation. If the steps JSON or the user input is untrusted, an attacker can achieve remote code execution, modify arbitrary files, and change process state (cwd). There are no signs of network exfiltration or hardcoded credentials in this fragment, but the command execution sink is sufficient to escalate to any of those behaviors if exploited. Recommendation: treat inputs (steps, file names, user-provided suggested commands) as untrusted; remove shell=True or use argument lists, validate and canonicalize file paths, avoid executing suggested commands automatically, and employ strict prompting and auditing. Overall this code is not itself evidently obfuscated or explicitly malicious, but it poses a significant supply-chain/runtime risk when given untrusted instructions.

Live on pypi for 5 days, 11 hours and 28 minutes before removal. Socket users were protected even while the package was live.

This file contains an obfuscated runtime loader/anti-tamper component that decrypts/loads payload bytes from resources or files, verifies them cryptographically, allocates executable memory, patches runtime/JIT structures or writes directly to process memory (including /proc/self/mem), and invokes the injected code. Those operations enable in-memory code injection and execution and are high-risk for supply chain security. If this package was expected to be a simple licensing wrapper, the native memory manipulation and JIT hooking are unexpected and dangerous. Treat this component as potentially malicious or at minimum as an extremely risky anti-tamper/packer: it should not be permitted without rigorous review and provenance confirmation.

This module behaves as a malicious proxy client: it forwards the provided API key, user prompts, and any local files to a hardcoded third-party IP over plaintext HTTP. This is high-risk credential and data exfiltration behavior that should be treated as a backdoor/supply-chain compromise. Do not use this package. If you have used it with real credentials or sensitive files, rotate affected API keys and assume data may have been leaked to the operator of 103.54.57.253.

This code implements direct data exfiltration: it reads data from a local module and immediately sends it to a hardcoded external endpoint. Treat it as malicious/backdoor behavior unless proven otherwise by inspecting ./reader and repository context. Remediate by removing the POST, auditing ./reader and repository history, checking for similar artifacts, and rotating any credentials that may have been exposed.

This module is malicious: it automatically scans the working directory for files matching /plta_|pltc_/ and uploads matching files to a hardcoded Telegram bot/chat. The behavior is data exfiltration triggered on import/run, uses embedded credentials, and lacks any legitimate configuration or consent mechanism. Treat this package as compromised: do not run it, remove it from builds/CI, revoke the bot token, rotate any exposed secrets, and investigate systems where it executed.

This script configures the host to transparently redirect all outbound HTTPS (TCP/443) traffic to a local port (127.0.0.1:4443) by modifying kernel networking and iptables rules. That behavior is strongly indicative of a local HTTPS interception/middleware setup and can be used maliciously to MITM TLS traffic — enabling credential theft, session capture, content tampering, or passive monitoring — depending on what local service listens on 4443. The script also enables IP forwarding (unnecessary for the redirect) and contains unusual SNAT usage. There is a syntax error in the final echo line which will likely break the script as provided. Overall, treat this code as high risk: it is capable of enabling system-wide interception of secure traffic and should not be run on trusted machines without full audit of the local listener and intent.

This module itself contains no obvious hidden backdoor or obfuscated malicious payload, but it intentionally executes external Python files found under multiple search paths (including user-writable locations like the current working directory and user home). That design introduces a high-risk supply-chain/plugin execution vector: untrusted plugin files named <domain>.py or package directories can run arbitrary code via exec_module and class instantiation. Recommend treating plugins from those paths as untrusted, restricting or validating plugin locations, using cryptographic signing or checksum verification, or executing plugins in an isolated process. Do not place sensitive credentials or run as privileged user when plugin discovery paths include writable directories.

This code performs unauthorized exfiltration of potentially sensitive credentials (the user's ~/.npmrc) and machine-identifying information to a hardcoded external endpoint over unencrypted HTTP. It should be treated as malicious or highly privacy-invasive. If present in a package, consider it compromised: remove the package, investigate exposure windows, and rotate any npm tokens or credentials that may have been stored in ~/.npmrc.

This file is part of a malicious package that exploits software distribution infrastructure for social engineering attacks. The assembly metadata contains extensive promotional content advertising illegal Snapchat account hacking services, including detailed descriptions of traffic-based attack methods against Snapchat servers. The file directs users to visit an external malicious website at hacksgames[.]online/Snap-Hack/ through embedded URLs in assembly descriptions. While containing no executable malicious code (only empty class implementations), it serves as a delivery mechanism to redirect users to potentially harmful external sites that could distribute malware, conduct phishing attacks, or engage in other malicious activities. This represents supply chain pollution by abusing legitimate package repositories to promote illegal services and poses significant security risks to users who may follow the embedded malicious links.

The code engages in potentially malicious behavior by collecting sensitive system information and sending it to a remote server without clear user consent. The hard-coded domain, data obfuscation, and lack of transparency raise significant privacy and security concerns. The risk score is high due to the invasive nature of the code.

Live on npm for 43 minutes before removal. Socket users were protected even while the package was live.

This code is malicious or at minimum behaves like a data-exfiltration/staging agent: it collects environment variables, system info, local files (/etc/passwd), command output, and EC2 metadata/IAM information and sends that entire dataset to a hardcoded external host (z.wbx.lt). Do not run this in production or on sensitive hosts. Treat the package as malicious and remove or block network egress to the indicated host if encountered.

Live on npm for 1 day, 16 hours and 56 minutes before removal. Socket users were protected even while the package was live.

The code appears to be heavily obfuscated with no clear functionality or purpose. It lacks any structured programming elements, making it unreadable and unanalyzable in its current form.

Live on npm for 2 days, 9 hours and 5 minutes before removal. Socket users were protected even while the package was live.

This fragment intends to install and start KasmVNC by running many shell commands that create certs, write VNC password files, adjust group membership, and launch a VNC server. The primary security issues are unsafe shell interpolation (command injection risk), programmatic persistence of a possibly predictable password, execution with sudo based on unvalidated env vars, starting a VNC server exposed on 0.0.0.0 with disabled/basic auth, and multiple unsafe filesystem operations performed via shell. There is no clear evidence of obfuscated or direct exfiltration malware, but the behavior can provide an unauthorized remote access vector (backdoor-like) if used maliciously. Do not run this code without fixing shell usage, validating inputs, using secure randomly generated passwords, enforcing proper file permissions, and not disabling authentication.

This is a high-risk destructive script that forcibly deletes /home/intel/dlstreamer without checks and prints a misleading success message. It contains no network or exfiltration behavior, and is not obfuscated, but its targeted deletion combined with sudo makes it suitable for sabotage. Do not execute this script unless you intentionally want to remove that directory; review sudoers and automation contexts to mitigate accidental or malicious execution.

The code is potentially malicious as it sends system-specific data (username) to an external domain, which could be used for unauthorized data collection or tracking. This represents a significant security risk.

Live on npm for 2 hours and 33 minutes before removal. Socket users were protected even while the package was live.

This code implements an insecure, unauthenticated RPC mechanism that allows remote clients to cause arbitrary code execution and exfiltrate files/system information. Using pickle over an untrusted network and invoking methods by client-supplied names are severe supply-chain/backdoor risks. Do not deploy or reuse this code in production; it should be treated as a backdoor/untrusted remote-execution component unless wrapped with strong authentication, authorization, sandboxing, and safe serialization.

The code operates as a Google Ads API integration wrapper, reading user input, constructing a GAQL-like query, and issuing a POST request to fetch user lists. While it does not demonstrate explicit malware, the combination of heavy obfuscation, dynamic string assembly, and potential injection surface from user-derived inputs requires careful audit of input validation, escaping for GAQL, and credential handling. The behavior warrants remediation to ensure robust input sanitization, removal of unnecessary obfuscation, and explicit error handling to avoid silent failures and potential data leakage.

This postinstall hook executes local code that, per the package metadata, is intended to encode and exfiltrate data to GitHub. Treat this as malicious: do not install or run without fully auditing index.js in a safe environment. There is a high risk of data exfiltration and other malicious activity.

This package will execute its bundled index.js during installation. Given the package name and description explicitly describing backdoor/persistence behavior, treat this as malicious. Do not install. Inspect the contents of index.js in a safe environment (offline/sandbox) if analysis is required, and if this was installed on production/self-hosted CI, assume compromise and perform incident response (rotate credentials, rebuild runners, check for persistence mechanisms and network egress).

The code appears to be a legitimate part of the SpiderMesh library, but it has potential security risks and unusual patterns that should be further reviewed and analyzed.

The code is designed to fetch and execute external payloads with minimal validation, enabling serious supply-chain and remote code execution risks. It lacks integrity checks (signatures, checksums), authentication, and robust error handling. The gunzip handling also appears flawed, which could cause runtime issues. The overall security risk is high for untrusted sources, and the malware likelihood is non-zero given the ability to run arbitrary downloaded code.

The code is performing actions consistent with malicious behavior by collecting and transmitting sensitive system information to an external server without user consent. This poses a significant security risk.

Live on pypi for 18 hours and 12 minutes before removal. Socket users were protected even while the package was live.

This script downloads a file from a remote server using curl. The URL contains a variable that is not defined in the script, which could indicate a typo or a malicious attempt to execute arbitrary code. The contents of the downloaded file should be reviewed for safety.

Live on npm for 9 hours and 32 minutes before removal. Socket users were protected even while the package was live.

The module contains high-risk operations: executing arbitrary shell commands via subprocess with shell=True and writing/appending to files without validation. If the steps JSON or the user input is untrusted, an attacker can achieve remote code execution, modify arbitrary files, and change process state (cwd). There are no signs of network exfiltration or hardcoded credentials in this fragment, but the command execution sink is sufficient to escalate to any of those behaviors if exploited. Recommendation: treat inputs (steps, file names, user-provided suggested commands) as untrusted; remove shell=True or use argument lists, validate and canonicalize file paths, avoid executing suggested commands automatically, and employ strict prompting and auditing. Overall this code is not itself evidently obfuscated or explicitly malicious, but it poses a significant supply-chain/runtime risk when given untrusted instructions.

Live on pypi for 5 days, 11 hours and 28 minutes before removal. Socket users were protected even while the package was live.

This file contains an obfuscated runtime loader/anti-tamper component that decrypts/loads payload bytes from resources or files, verifies them cryptographically, allocates executable memory, patches runtime/JIT structures or writes directly to process memory (including /proc/self/mem), and invokes the injected code. Those operations enable in-memory code injection and execution and are high-risk for supply chain security. If this package was expected to be a simple licensing wrapper, the native memory manipulation and JIT hooking are unexpected and dangerous. Treat this component as potentially malicious or at minimum as an extremely risky anti-tamper/packer: it should not be permitted without rigorous review and provenance confirmation.

This module behaves as a malicious proxy client: it forwards the provided API key, user prompts, and any local files to a hardcoded third-party IP over plaintext HTTP. This is high-risk credential and data exfiltration behavior that should be treated as a backdoor/supply-chain compromise. Do not use this package. If you have used it with real credentials or sensitive files, rotate affected API keys and assume data may have been leaked to the operator of 103.54.57.253.

This code implements direct data exfiltration: it reads data from a local module and immediately sends it to a hardcoded external endpoint. Treat it as malicious/backdoor behavior unless proven otherwise by inspecting ./reader and repository context. Remediate by removing the POST, auditing ./reader and repository history, checking for similar artifacts, and rotating any credentials that may have been exposed.

This module is malicious: it automatically scans the working directory for files matching /plta_|pltc_/ and uploads matching files to a hardcoded Telegram bot/chat. The behavior is data exfiltration triggered on import/run, uses embedded credentials, and lacks any legitimate configuration or consent mechanism. Treat this package as compromised: do not run it, remove it from builds/CI, revoke the bot token, rotate any exposed secrets, and investigate systems where it executed.

This script configures the host to transparently redirect all outbound HTTPS (TCP/443) traffic to a local port (127.0.0.1:4443) by modifying kernel networking and iptables rules. That behavior is strongly indicative of a local HTTPS interception/middleware setup and can be used maliciously to MITM TLS traffic — enabling credential theft, session capture, content tampering, or passive monitoring — depending on what local service listens on 4443. The script also enables IP forwarding (unnecessary for the redirect) and contains unusual SNAT usage. There is a syntax error in the final echo line which will likely break the script as provided. Overall, treat this code as high risk: it is capable of enabling system-wide interception of secure traffic and should not be run on trusted machines without full audit of the local listener and intent.

This module itself contains no obvious hidden backdoor or obfuscated malicious payload, but it intentionally executes external Python files found under multiple search paths (including user-writable locations like the current working directory and user home). That design introduces a high-risk supply-chain/plugin execution vector: untrusted plugin files named <domain>.py or package directories can run arbitrary code via exec_module and class instantiation. Recommend treating plugins from those paths as untrusted, restricting or validating plugin locations, using cryptographic signing or checksum verification, or executing plugins in an isolated process. Do not place sensitive credentials or run as privileged user when plugin discovery paths include writable directories.

This code performs unauthorized exfiltration of potentially sensitive credentials (the user's ~/.npmrc) and machine-identifying information to a hardcoded external endpoint over unencrypted HTTP. It should be treated as malicious or highly privacy-invasive. If present in a package, consider it compromised: remove the package, investigate exposure windows, and rotate any npm tokens or credentials that may have been stored in ~/.npmrc.

This file is part of a malicious package that exploits software distribution infrastructure for social engineering attacks. The assembly metadata contains extensive promotional content advertising illegal Snapchat account hacking services, including detailed descriptions of traffic-based attack methods against Snapchat servers. The file directs users to visit an external malicious website at hacksgames[.]online/Snap-Hack/ through embedded URLs in assembly descriptions. While containing no executable malicious code (only empty class implementations), it serves as a delivery mechanism to redirect users to potentially harmful external sites that could distribute malware, conduct phishing attacks, or engage in other malicious activities. This represents supply chain pollution by abusing legitimate package repositories to promote illegal services and poses significant security risks to users who may follow the embedded malicious links.

The code engages in potentially malicious behavior by collecting sensitive system information and sending it to a remote server without clear user consent. The hard-coded domain, data obfuscation, and lack of transparency raise significant privacy and security concerns. The risk score is high due to the invasive nature of the code.

Live on npm for 43 minutes before removal. Socket users were protected even while the package was live.

This code is malicious or at minimum behaves like a data-exfiltration/staging agent: it collects environment variables, system info, local files (/etc/passwd), command output, and EC2 metadata/IAM information and sends that entire dataset to a hardcoded external host (z.wbx.lt). Do not run this in production or on sensitive hosts. Treat the package as malicious and remove or block network egress to the indicated host if encountered.

Live on npm for 1 day, 16 hours and 56 minutes before removal. Socket users were protected even while the package was live.

The code appears to be heavily obfuscated with no clear functionality or purpose. It lacks any structured programming elements, making it unreadable and unanalyzable in its current form.

Live on npm for 2 days, 9 hours and 5 minutes before removal. Socket users were protected even while the package was live.

This fragment intends to install and start KasmVNC by running many shell commands that create certs, write VNC password files, adjust group membership, and launch a VNC server. The primary security issues are unsafe shell interpolation (command injection risk), programmatic persistence of a possibly predictable password, execution with sudo based on unvalidated env vars, starting a VNC server exposed on 0.0.0.0 with disabled/basic auth, and multiple unsafe filesystem operations performed via shell. There is no clear evidence of obfuscated or direct exfiltration malware, but the behavior can provide an unauthorized remote access vector (backdoor-like) if used maliciously. Do not run this code without fixing shell usage, validating inputs, using secure randomly generated passwords, enforcing proper file permissions, and not disabling authentication.

This is a high-risk destructive script that forcibly deletes /home/intel/dlstreamer without checks and prints a misleading success message. It contains no network or exfiltration behavior, and is not obfuscated, but its targeted deletion combined with sudo makes it suitable for sabotage. Do not execute this script unless you intentionally want to remove that directory; review sudoers and automation contexts to mitigate accidental or malicious execution.

The code is potentially malicious as it sends system-specific data (username) to an external domain, which could be used for unauthorized data collection or tracking. This represents a significant security risk.

Live on npm for 2 hours and 33 minutes before removal. Socket users were protected even while the package was live.

This code implements an insecure, unauthenticated RPC mechanism that allows remote clients to cause arbitrary code execution and exfiltrate files/system information. Using pickle over an untrusted network and invoking methods by client-supplied names are severe supply-chain/backdoor risks. Do not deploy or reuse this code in production; it should be treated as a backdoor/untrusted remote-execution component unless wrapped with strong authentication, authorization, sandboxing, and safe serialization.