Secure your dependencies. Ship with confidence.

This package contains heavily obfuscated malicious code disguised as a legitimate Solana wallet utility. The hidden payload executes arbitrary code by default and poses extreme security risk, especially for cryptocurrency operations. The obfuscation techniques and silent execution patterns are classic malware indicators.

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

This file contains code that reverses a string, decodes it from base64, decompresses it with zlib, and then executes it via exec(). Such obfuscation is a common tactic in malicious scripts to hide their true functionality, which can include data exfiltration, system compromise, or other unauthorized activities. No specific domain or IP address references were found in the decoded payload, but the obfuscation strongly indicates malicious intent.

The script exhibits clear malicious behavior by sending sensitive system information to an external server without user consent. This poses a significant security risk.

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

The script poses a high security risk as malware due to its ability to alter disk partitions without user interaction, leading to data loss or system damage.

The code exhibits clear malicious behavior by collecting and transmitting sensitive user data without consent. The presence of an infinite loop raises additional concerns about resource management. Overall, this code poses a significant security risk and should not be used.

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

The code is designed to exfiltrate sensitive system and user data to a remote server without user consent, indicating malicious intent. This poses a significant security risk.

The code snippet exhibits suspicious behavior by making an unencrypted HTTP request to a raw IP address on a non-standard port, which could indicate potential malicious activity such as data exfiltration or command and control communication. Although no direct malware code or obfuscation is present, the network activity alone warrants a moderate to high security risk rating. The existing reports are invalid and provide no useful information. Further investigation of the full codebase and network traffic is recommended.

The script is designed to send sensitive information about the user and the system to an external server, which poses a serious security risk and is indicative of malicious behavior.

Live on npm for 20 days, 15 hours and 58 minutes before removal. Socket users were protected even while the package was live.

The code includes a hardcoded API key, which poses a security risk if the key is sensitive and should not be public. The error handling could also potentially leak sensitive information. These concerns could be mitigated by removing the hardcoded API key and improving error handling.

Live on PyPI for 1 day, 20 hours and 41 minutes before removal. Socket users were protected even while the package was live.

The source code itself does not contain explicit malicious code, but the assembly metadata promotes a suspicious Fortnite skin generator hack with a phishing URL. This strongly indicates malicious intent or scam. The lack of actual code and presence of spammy metadata suggest this package is unsafe and likely malicious. The existing reports are invalid and provide no useful information. This package should be flagged as high risk and potentially malicious.

The code is highly suspicious due to its use of obfuscation, decryption, and execution of hidden code. It poses a significant security risk, especially to Windows systems, and is indicative of potentially malicious behavior.

Live on PyPI for 1 hour and 52 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.

The code contains functions that can be exploited for malicious purposes, such as executing arbitrary shellcode and side-loading libraries. These capabilities justify a high malware and risk score.

The code provides utility functions for URL manipulation, but it lacks input validation and sanitization, posing a risk of URL-related vulnerabilities. Proper input validation and sanitization should be implemented to mitigate security risks.

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

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 16 days, 17 hours and 9 minutes before removal. Socket users were protected even while the package was live.

The code is highly suspicious due to its unauthorized collection and transmission of system and project data to external servers. This behavior aligns with malicious intent, posing a significant security risk.

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

The code exhibits clear malicious behavior by collecting and transmitting sensitive user data without consent. This poses a significant security risk, warranting high malware and risk scores.

Possible typosquat of [azure](https://socket.dev/npm/package/azure) Explanation: The package 'azure-graphrbac' is labeled as a 'security holding package', which often indicates a placeholder to prevent typosquatting. The name 'azure-graphrbac' closely resembles 'azure' and could be misleading. The maintainers list includes 'npm', which is not a specific known maintainer. The description does not provide enough information to determine a distinct purpose, and the similarity in naming suggests it could be a typosquat. azure-graphrbac is a security-holding package

Live on npm for 1 hour and 21 minutes before removal. Socket users were protected even while the package was live.

The code exhibits potentially malicious behavior by collecting system information and sending it to a suspicious domain. This behavior raises serious privacy and security concerns.

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

The code imports modules for HTTP requests (axios), form data handling (form-data), and ZIP file creation (jszip). It defines functions that collect data—including zipped image files from 'runners' and JSON data containing 'minimizer' and 'fuzzer' information—and sends it to an external server using HTTP POST requests via axios. The destination URL is constructed by reversing and Base64-decoding an encoded string, resulting in an obfuscated URL that resolves to an external server at IP address 135[.]148[.]42[.]232 on port 443 (e.g., 'http://135[.]148[.]42[.]232:443/api1'). This obfuscation hides the true destination of the data, making it difficult to verify the legitimacy of the server receiving the information. The code's behavior indicates potential data exfiltration and malicious intent, aligning with the characteristics of malware.

The script runs 'index.js' and silences all output, which could be a method to hide malicious actions or errors. The safety of this script depends on the contents of 'index.js'.

The source code is performing malicious activities by exfiltrating sensitive system information to a suspicious domain (pingb.in). This poses a significant security risk.

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

This file automates login to facebook[.]com and attempts to bypass built-in security prompts or notifications, collecting and storing user credentials (including cookies, tokens, and environment variables) without adequate safeguards. It manipulates HTTP requests and responses to sidestep protective checks and can facilitate unauthorized or automated access to user accounts, posing a significant security risk. Sensitive input like user credentials may also be stored or transmitted in plaintext, increasing the potential for credential theft or misuse.

The code exhibits malicious behavior by collecting and sending sensitive system information, including directory paths, OS hostname, and user information, as well as contents of 'package.json' files to remote servers. This represents a clear privacy violation and potential data theft.

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

The code exhibits malicious behavior by collecting and sending sensitive system data to a remote server without user consent. This poses a significant security risk due to the potential misuse of the exfiltrated data.

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

This package contains heavily obfuscated malicious code disguised as a legitimate Solana wallet utility. The hidden payload executes arbitrary code by default and poses extreme security risk, especially for cryptocurrency operations. The obfuscation techniques and silent execution patterns are classic malware indicators.

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

This file contains code that reverses a string, decodes it from base64, decompresses it with zlib, and then executes it via exec(). Such obfuscation is a common tactic in malicious scripts to hide their true functionality, which can include data exfiltration, system compromise, or other unauthorized activities. No specific domain or IP address references were found in the decoded payload, but the obfuscation strongly indicates malicious intent.

The script exhibits clear malicious behavior by sending sensitive system information to an external server without user consent. This poses a significant security risk.

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

The script poses a high security risk as malware due to its ability to alter disk partitions without user interaction, leading to data loss or system damage.

The code exhibits clear malicious behavior by collecting and transmitting sensitive user data without consent. The presence of an infinite loop raises additional concerns about resource management. Overall, this code poses a significant security risk and should not be used.

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

The code is designed to exfiltrate sensitive system and user data to a remote server without user consent, indicating malicious intent. This poses a significant security risk.

The code snippet exhibits suspicious behavior by making an unencrypted HTTP request to a raw IP address on a non-standard port, which could indicate potential malicious activity such as data exfiltration or command and control communication. Although no direct malware code or obfuscation is present, the network activity alone warrants a moderate to high security risk rating. The existing reports are invalid and provide no useful information. Further investigation of the full codebase and network traffic is recommended.

The script is designed to send sensitive information about the user and the system to an external server, which poses a serious security risk and is indicative of malicious behavior.

Live on npm for 20 days, 15 hours and 58 minutes before removal. Socket users were protected even while the package was live.

The code includes a hardcoded API key, which poses a security risk if the key is sensitive and should not be public. The error handling could also potentially leak sensitive information. These concerns could be mitigated by removing the hardcoded API key and improving error handling.

Live on PyPI for 1 day, 20 hours and 41 minutes before removal. Socket users were protected even while the package was live.

The source code itself does not contain explicit malicious code, but the assembly metadata promotes a suspicious Fortnite skin generator hack with a phishing URL. This strongly indicates malicious intent or scam. The lack of actual code and presence of spammy metadata suggest this package is unsafe and likely malicious. The existing reports are invalid and provide no useful information. This package should be flagged as high risk and potentially malicious.

The code is highly suspicious due to its use of obfuscation, decryption, and execution of hidden code. It poses a significant security risk, especially to Windows systems, and is indicative of potentially malicious behavior.

Live on PyPI for 1 hour and 52 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.

The code contains functions that can be exploited for malicious purposes, such as executing arbitrary shellcode and side-loading libraries. These capabilities justify a high malware and risk score.

The code provides utility functions for URL manipulation, but it lacks input validation and sanitization, posing a risk of URL-related vulnerabilities. Proper input validation and sanitization should be implemented to mitigate security risks.

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

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 16 days, 17 hours and 9 minutes before removal. Socket users were protected even while the package was live.

The code is highly suspicious due to its unauthorized collection and transmission of system and project data to external servers. This behavior aligns with malicious intent, posing a significant security risk.

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

The code exhibits clear malicious behavior by collecting and transmitting sensitive user data without consent. This poses a significant security risk, warranting high malware and risk scores.

Possible typosquat of [azure](https://socket.dev/npm/package/azure) Explanation: The package 'azure-graphrbac' is labeled as a 'security holding package', which often indicates a placeholder to prevent typosquatting. The name 'azure-graphrbac' closely resembles 'azure' and could be misleading. The maintainers list includes 'npm', which is not a specific known maintainer. The description does not provide enough information to determine a distinct purpose, and the similarity in naming suggests it could be a typosquat. azure-graphrbac is a security-holding package

Live on npm for 1 hour and 21 minutes before removal. Socket users were protected even while the package was live.

The code exhibits potentially malicious behavior by collecting system information and sending it to a suspicious domain. This behavior raises serious privacy and security concerns.

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

The code imports modules for HTTP requests (axios), form data handling (form-data), and ZIP file creation (jszip). It defines functions that collect data—including zipped image files from 'runners' and JSON data containing 'minimizer' and 'fuzzer' information—and sends it to an external server using HTTP POST requests via axios. The destination URL is constructed by reversing and Base64-decoding an encoded string, resulting in an obfuscated URL that resolves to an external server at IP address 135[.]148[.]42[.]232 on port 443 (e.g., 'http://135[.]148[.]42[.]232:443/api1'). This obfuscation hides the true destination of the data, making it difficult to verify the legitimacy of the server receiving the information. The code's behavior indicates potential data exfiltration and malicious intent, aligning with the characteristics of malware.

The script runs 'index.js' and silences all output, which could be a method to hide malicious actions or errors. The safety of this script depends on the contents of 'index.js'.

The source code is performing malicious activities by exfiltrating sensitive system information to a suspicious domain (pingb.in). This poses a significant security risk.

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

This file automates login to facebook[.]com and attempts to bypass built-in security prompts or notifications, collecting and storing user credentials (including cookies, tokens, and environment variables) without adequate safeguards. It manipulates HTTP requests and responses to sidestep protective checks and can facilitate unauthorized or automated access to user accounts, posing a significant security risk. Sensitive input like user credentials may also be stored or transmitted in plaintext, increasing the potential for credential theft or misuse.

The code exhibits malicious behavior by collecting and sending sensitive system information, including directory paths, OS hostname, and user information, as well as contents of 'package.json' files to remote servers. This represents a clear privacy violation and potential data theft.

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

The code exhibits malicious behavior by collecting and sending sensitive system data to a remote server without user consent. This poses a significant security risk due to the potential misuse of the exfiltrated data.

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