Secure your dependencies. Ship with confidence.

The fragment shows a local network call followed by a log write. While not conclusively malicious, the pattern resembles beaconing or data extraction vectors when used with a placeholder port and a local endpoint. Treat as suspicious in a supply-chain context; verify APACHEPORT value, the intended purpose of SendReminder.php, and whether this behavior is documented in the project. Enforce least-privilege, validate provenance, and consider restricting local network egress for build/runtime environments.

This module implements a high-impact installer/launcher pipeline: it downloads a remote ZIP from a fixed CDN, unzips it locally, and then executes an installer executable via execFile. In this code, there is no visible integrity/signature/hash verification of the downloaded archive before extraction/execution, which is a significant supply-chain/RCE risk if the artifact or hosting is compromised. Additionally, the Electron window is configured with nodeIntegration:true and webSecurity:false, increasing the blast radius of any renderer compromise, and several privileged IPC handlers can trigger the download/unzip/execute workflow. The 'Game.SendLogs' functionality may also expose or export diagnostic information to the desktop.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as protestware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

This package will execute postinstall.js on install. Executing a package-provided script is a normal practice for setup tasks, but it is a common vector for malicious behavior (telemetry, data exfiltration, adding hooks, installing additional packages, starting background processes, or opening network connections). You should inspect the contents of postinstall.js before installing. Absent that inspection, treat this as a moderate security risk.

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

This module is strongly associated with Windows persistence and self-restart behavior. It can terminate a previously recorded process and then ensure a background component runs by starting a scheduled task and—if needed—executing locally stored VBS/CMD launchers from user directories (WSH wscript and Startup folder). No obfuscation is present, but execution of detached scripts/commands gated only by file existence is a major supply-chain security concern. The actual maliciousness depends on what daemon-launcher.vbs and imcodes-daemon.cmd contain, which are not shown here.

This module zips a local directory and uploads it to a specific S3 bucket. The code contains hardcoded AWS credentials and a hardcoded bucket name, which is a severe security issue and could enable data exfiltration if these credentials are valid. There are additional problems: a likely return-value bug (undefined variable s3_ke), possible insufficient path-safety around symlinks, and verbose logging of paths. There is no evidence of obfuscation or active payloads like reverse shells or eval-based code execution. Treat this package as high-risk until credentials are removed/rotated and the code is corrected and reviewed.

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

The module performs an automatic, side-effectful installation: if a specific HKCU registry value is missing it downloads a DLL from a hardcoded remote URL and writes it to C:\Temp\Temp2, then records the path in the registry under HKCU\\Software\\HNC\\HwpAutomation\\Modules. This behavior is dangerous: it persists a native binary without validation and can enable execution by other HWP automation components. Coupled with malformed/truncated code later in the file, the fragment is suspicious and should not be trusted. Recommend blocking execution, obtaining the DLL from a verified source, and requiring explicit, audited installation steps (with signatures/checksums) before allowing such behavior.

This module performs credential-based authentication to a remote service and then requests a likely sensitive database dump endpoint using persisted cookies. The combination of predictable /tmp handling for credentials/cookies, disabled TLS verification (-k), and bash tracing (-x) makes it particularly risky in a supply-chain context. While it could be intended for legitimate administrative backup/export, the explicit dbdump retrieval sequence strongly resembles an automated credential-driven data extraction workflow and should be reviewed/controlled tightly.

`lotusbail` is a malicious npm package that masquerades as a WhatsApp Web API library by forking legitimate Baileys-based code and preserving working messaging functionality. In addition to normal API behavior, it inserts a wrapper around the WhatsApp WebSocket client so that all traffic passing through the library is duplicated for collection. Reported data theft includes WhatsApp authentication tokens and session keys, full message content (sent/received and historical), contact lists (including phone numbers), and transferred media/files. The package also attempts to establish persistent unauthorized access by hijacking the WhatsApp device-linking (“pairing”) workflow using a hardcoded pairing code, effectively linking an attacker-controlled device to the victim’s account; removing the npm dependency does not automatically remove the linked device. To hinder detection, the exfiltration endpoint is hidden behind multiple obfuscation layers, collected data is encrypted (including a custom RSA implementation), and the code includes anti-debugging traps designed to disrupt analysis.

High risk. The package runs an extract-tokens script automatically on install (postinstall) and provides tooling that can harvest tokens and send invites. Combined with screen-capture capability and the suspicious self-dependency, this package is likely to perform credential theft and unsolicited account actions. Do not install on any machine with credentials or sensitive data; inspect the referenced scripts (bin/extract-tokens.js, bin/preinstall.js, bin/start-bot.js, etc.) in a safe, offline environment before considering use.

The code runs an executable file when the module is loaded. It uses the 'exec' function to execute a command, which could be a security risk if untrusted data is passed to it. The hard-coded executable file name is also an anomaly that could be a security risk if the file is malicious.

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

The provided module is a clear denial-of-service (HTTP GET flood) implementation: multithreaded sockets repeatedly connect to and send requests to a target host and port with no safeguards. It is malicious by purpose and poses a high supply-chain/security risk. Do not include or execute this code in trusted environments. Treat packages containing this code as malicious or severely dangerous.

This preinstall script is malicious: it collects and transmits sensitive system information (including /etc/shadow) to an external endpoint during npm install. Installing this package will leak credentials and system data and should be considered high-risk. Do not install or run on any system with sensitive data; investigate and remove any exposure if already executed.

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

This code performs targeted local reconnaissance and exfiltrates environment and user data (including the presence of company-related entries in shell histories and directory listings) to a hardcoded external OAST domain over unencrypted HTTP. The behavior is clearly malicious or at minimum privacy-invasive and unsuitable for a dependency. Treat this package as a supply-chain compromise: remove it, block the endpoint, and investigate systems where it executed for potential data exposure.

The code is not overtly malicious but contains high-risk deserialization patterns: dynamic, data-driven class import and reconstruction of objects (AbstractFileSystem.from_dict and constructor calls) combined with default inclusion of passwords. If untrusted JSON can reach FilesystemJSONDecoder, an attacker could cause arbitrary imports and trigger side effects or credential disclosure. Treat this module as unsafe for untrusted input unless mitigations (allowlist, disable password emission, input validation) are applied. The fragment appears incomplete which lowers full-confidence assessment.

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

This module is a reverse proxy designed to enable phishing: it strips security headers, downgrades cookie security, injects JavaScript payloads, rewrites URLs to a phishing domain, logs cookies and session identifiers, and accepts invalid TLS certificates. These behaviors constitute active malicious functionality for credential/session capture and user tracking. The code should be considered dangerous and unsuitable for use in normal applications. Use only with explicit authorization in controlled environments.

This setup.py contains explicit, malicious data-exfiltration behavior executed during package installation. It reads a likely sensitive file (/flag.txt) and posts its contents to a hardcoded external webhook, while suppressing errors to remain stealthy. Treat this package as malicious: do not install it, remove it from affected systems, and investigate any environments where it was installed for leaked secrets or further compromise.

The code collects and sends sensitive system information to potentially suspicious external domains without user consent, which is a significant security risk. The use of 'rejectUnauthorized: false' further exacerbates the risk by disabling SSL/TLS certificate validation.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as malware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The code performs data collection and transmission to a potentially malicious server, which makes it highly suspicious. The code uses a hardcoded suspicious domain, collects user information without consent, and sends the data to an external server. This can lead to severe privacy violation and data leak issues.

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

This module implements a GUI chat application that integrates with OpenAI and provides features that allow arbitrary Python and shell command execution based on selected text or user input, and loads plugins from the filesystem. I did not find explicit hardcoded backdoor/network exfiltration to a suspicious external domain. However, the code exposes powerful dangerous sinks (exec, eval, subprocess.run(..., shell=True), os.system) directly to user-supplied or file-supplied content without sandboxing. This is a high security risk for accidental misuse or malicious plugins/content; treat the package as potentially dangerous in contexts where untrusted data or plugins may be present. Recommended mitigation: remove or require explicit confirmation for run-as-command features, sandbox or restrict exec/context, avoid shell=True, avoid eval, and never auto-run plugin code from untrusted locations.

This module exposes an extremely high-risk remote control surface: it can spawn an interactive shell (PTY with fallback), accept client-provided base64 input to that shell, and stream the resulting output back to the client over WebSocket—creating a bidirectional remote command execution channel. It also exposes PM2 administrative operations and log retrieval/flush using client-controlled parameters. If strong authorization and auditing are not enforced elsewhere, this is consistent with backdoor/RCE capability and represents a severe supply-chain security concern.

The code contains dynamic URL alterations and uses 'os.system' with user inputs, posing a security risk. It is recommended to review the code for safer alternatives.

This module is a deliberate destructive utility that corrupts all .zip files in a specified directory by truncating each archive to half its size and appending repeated junk data. While it lacks common malware features like networking or data exfiltration, the behavior is strongly indicative of sabotage and would be unacceptable in most software supply-chain contexts due to its potential to break builds, deployments, or artifact integrity.

The fragment shows a local network call followed by a log write. While not conclusively malicious, the pattern resembles beaconing or data extraction vectors when used with a placeholder port and a local endpoint. Treat as suspicious in a supply-chain context; verify APACHEPORT value, the intended purpose of SendReminder.php, and whether this behavior is documented in the project. Enforce least-privilege, validate provenance, and consider restricting local network egress for build/runtime environments.

This module implements a high-impact installer/launcher pipeline: it downloads a remote ZIP from a fixed CDN, unzips it locally, and then executes an installer executable via execFile. In this code, there is no visible integrity/signature/hash verification of the downloaded archive before extraction/execution, which is a significant supply-chain/RCE risk if the artifact or hosting is compromised. Additionally, the Electron window is configured with nodeIntegration:true and webSecurity:false, increasing the blast radius of any renderer compromise, and several privileged IPC handlers can trigger the download/unzip/execute workflow. The 'Game.SendLogs' functionality may also expose or export diagnostic information to the desktop.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as protestware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

This package will execute postinstall.js on install. Executing a package-provided script is a normal practice for setup tasks, but it is a common vector for malicious behavior (telemetry, data exfiltration, adding hooks, installing additional packages, starting background processes, or opening network connections). You should inspect the contents of postinstall.js before installing. Absent that inspection, treat this as a moderate security risk.

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

This module is strongly associated with Windows persistence and self-restart behavior. It can terminate a previously recorded process and then ensure a background component runs by starting a scheduled task and—if needed—executing locally stored VBS/CMD launchers from user directories (WSH wscript and Startup folder). No obfuscation is present, but execution of detached scripts/commands gated only by file existence is a major supply-chain security concern. The actual maliciousness depends on what daemon-launcher.vbs and imcodes-daemon.cmd contain, which are not shown here.

This module zips a local directory and uploads it to a specific S3 bucket. The code contains hardcoded AWS credentials and a hardcoded bucket name, which is a severe security issue and could enable data exfiltration if these credentials are valid. There are additional problems: a likely return-value bug (undefined variable s3_ke), possible insufficient path-safety around symlinks, and verbose logging of paths. There is no evidence of obfuscation or active payloads like reverse shells or eval-based code execution. Treat this package as high-risk until credentials are removed/rotated and the code is corrected and reviewed.

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

The module performs an automatic, side-effectful installation: if a specific HKCU registry value is missing it downloads a DLL from a hardcoded remote URL and writes it to C:\Temp\Temp2, then records the path in the registry under HKCU\\Software\\HNC\\HwpAutomation\\Modules. This behavior is dangerous: it persists a native binary without validation and can enable execution by other HWP automation components. Coupled with malformed/truncated code later in the file, the fragment is suspicious and should not be trusted. Recommend blocking execution, obtaining the DLL from a verified source, and requiring explicit, audited installation steps (with signatures/checksums) before allowing such behavior.

This module performs credential-based authentication to a remote service and then requests a likely sensitive database dump endpoint using persisted cookies. The combination of predictable /tmp handling for credentials/cookies, disabled TLS verification (-k), and bash tracing (-x) makes it particularly risky in a supply-chain context. While it could be intended for legitimate administrative backup/export, the explicit dbdump retrieval sequence strongly resembles an automated credential-driven data extraction workflow and should be reviewed/controlled tightly.

`lotusbail` is a malicious npm package that masquerades as a WhatsApp Web API library by forking legitimate Baileys-based code and preserving working messaging functionality. In addition to normal API behavior, it inserts a wrapper around the WhatsApp WebSocket client so that all traffic passing through the library is duplicated for collection. Reported data theft includes WhatsApp authentication tokens and session keys, full message content (sent/received and historical), contact lists (including phone numbers), and transferred media/files. The package also attempts to establish persistent unauthorized access by hijacking the WhatsApp device-linking (“pairing”) workflow using a hardcoded pairing code, effectively linking an attacker-controlled device to the victim’s account; removing the npm dependency does not automatically remove the linked device. To hinder detection, the exfiltration endpoint is hidden behind multiple obfuscation layers, collected data is encrypted (including a custom RSA implementation), and the code includes anti-debugging traps designed to disrupt analysis.

High risk. The package runs an extract-tokens script automatically on install (postinstall) and provides tooling that can harvest tokens and send invites. Combined with screen-capture capability and the suspicious self-dependency, this package is likely to perform credential theft and unsolicited account actions. Do not install on any machine with credentials or sensitive data; inspect the referenced scripts (bin/extract-tokens.js, bin/preinstall.js, bin/start-bot.js, etc.) in a safe, offline environment before considering use.

The code runs an executable file when the module is loaded. It uses the 'exec' function to execute a command, which could be a security risk if untrusted data is passed to it. The hard-coded executable file name is also an anomaly that could be a security risk if the file is malicious.

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

The provided module is a clear denial-of-service (HTTP GET flood) implementation: multithreaded sockets repeatedly connect to and send requests to a target host and port with no safeguards. It is malicious by purpose and poses a high supply-chain/security risk. Do not include or execute this code in trusted environments. Treat packages containing this code as malicious or severely dangerous.

This preinstall script is malicious: it collects and transmits sensitive system information (including /etc/shadow) to an external endpoint during npm install. Installing this package will leak credentials and system data and should be considered high-risk. Do not install or run on any system with sensitive data; investigate and remove any exposure if already executed.

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

This code performs targeted local reconnaissance and exfiltrates environment and user data (including the presence of company-related entries in shell histories and directory listings) to a hardcoded external OAST domain over unencrypted HTTP. The behavior is clearly malicious or at minimum privacy-invasive and unsuitable for a dependency. Treat this package as a supply-chain compromise: remove it, block the endpoint, and investigate systems where it executed for potential data exposure.

The code is not overtly malicious but contains high-risk deserialization patterns: dynamic, data-driven class import and reconstruction of objects (AbstractFileSystem.from_dict and constructor calls) combined with default inclusion of passwords. If untrusted JSON can reach FilesystemJSONDecoder, an attacker could cause arbitrary imports and trigger side effects or credential disclosure. Treat this module as unsafe for untrusted input unless mitigations (allowlist, disable password emission, input validation) are applied. The fragment appears incomplete which lowers full-confidence assessment.

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

This module is a reverse proxy designed to enable phishing: it strips security headers, downgrades cookie security, injects JavaScript payloads, rewrites URLs to a phishing domain, logs cookies and session identifiers, and accepts invalid TLS certificates. These behaviors constitute active malicious functionality for credential/session capture and user tracking. The code should be considered dangerous and unsuitable for use in normal applications. Use only with explicit authorization in controlled environments.

This setup.py contains explicit, malicious data-exfiltration behavior executed during package installation. It reads a likely sensitive file (/flag.txt) and posts its contents to a hardcoded external webhook, while suppressing errors to remain stealthy. Treat this package as malicious: do not install it, remove it from affected systems, and investigate any environments where it was installed for leaked secrets or further compromise.

The code collects and sends sensitive system information to potentially suspicious external domains without user consent, which is a significant security risk. The use of 'rejectUnauthorized: false' further exacerbates the risk by disabling SSL/TLS certificate validation.

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

The package contains a hidden payload that targets Russian language users visiting Russian and Belarusian sites. For those users, it will disable user interaction and play a looping audio of the Ukrainian anthem after 3 days. Therefore, it is marked as malware only because it freezes interactions for many users. This behavior is not disclosed in any documentation of the package and seriously disrupts user experience.

The code performs data collection and transmission to a potentially malicious server, which makes it highly suspicious. The code uses a hardcoded suspicious domain, collects user information without consent, and sends the data to an external server. This can lead to severe privacy violation and data leak issues.

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

This module implements a GUI chat application that integrates with OpenAI and provides features that allow arbitrary Python and shell command execution based on selected text or user input, and loads plugins from the filesystem. I did not find explicit hardcoded backdoor/network exfiltration to a suspicious external domain. However, the code exposes powerful dangerous sinks (exec, eval, subprocess.run(..., shell=True), os.system) directly to user-supplied or file-supplied content without sandboxing. This is a high security risk for accidental misuse or malicious plugins/content; treat the package as potentially dangerous in contexts where untrusted data or plugins may be present. Recommended mitigation: remove or require explicit confirmation for run-as-command features, sandbox or restrict exec/context, avoid shell=True, avoid eval, and never auto-run plugin code from untrusted locations.

This module exposes an extremely high-risk remote control surface: it can spawn an interactive shell (PTY with fallback), accept client-provided base64 input to that shell, and stream the resulting output back to the client over WebSocket—creating a bidirectional remote command execution channel. It also exposes PM2 administrative operations and log retrieval/flush using client-controlled parameters. If strong authorization and auditing are not enforced elsewhere, this is consistent with backdoor/RCE capability and represents a severe supply-chain security concern.

The code contains dynamic URL alterations and uses 'os.system' with user inputs, posing a security risk. It is recommended to review the code for safer alternatives.

This module is a deliberate destructive utility that corrupts all .zip files in a specified directory by truncating each archive to half its size and appending repeated junk data. While it lacks common malware features like networking or data exfiltration, the behavior is strongly indicative of sabotage and would be unacceptable in most software supply-chain contexts due to its potential to break builds, deployments, or artifact integrity.