Secure your dependencies. Ship with confidence.

Malicious code in orbit-tracking (npm) Source: ghsa-malware (b514c540f5d1347c7573a09c60655ff0d5981f14a3e86f7d0bfe30316c2e2894) 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.

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

Malicious code in phpmyadmin (npm) Source: ghsa-malware (1554572f62f66f781c39beac2b19170401216f0d4d9a828358a89793b7fdcc46) 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.

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

The code exhibits potential security risks related to user authentication and data handling, particularly with the CAPTCHA cracking functionality. While there are no clear indicators of malware, the use of external libraries and dynamic code execution raises concerns. The overall risk is moderate, and further scrutiny is recommended.

Malicious code in pp-amount-field (npm) Source: ghsa-malware (25fda0186ce26a0871fe78f3ec99900b6d2f42baa4d4ecb6ea1590d3076b8386) 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.

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

Malicious code in signup-ui-core (npm) Source: ghsa-malware (5efd0acaccf47da92b3f4cb09e80de3b56ec88952a48030330e28d308b983e36) 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.

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

Malicious code in constantparam (npm) Source: ghsa-malware (d70c96d26cc546890595df8beea2035e8d6a30089ede37bc41acbaa37f2a9186) 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.

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

Malicious code in lolo1122 (npm) Source: ghsa-malware (42db12ae19e91064867283ce996f4b0e498f5633f088a0d8eeb3459c024dfa8c) 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.

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

Malicious code in share-client (npm) Source: ghsa-malware (ba664ab24090b0fcbea9d3c7c58134f47472535eba4ff9d4a65946aa5efad8ed) 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.

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

Malicious code in eosio-signer (PyPI)

Live on PyPI for 14 hours and 52 minutes before removal. Socket users were protected even while the package was live.

Malicious code in iotspaces (npm) Source: ghsa-malware (9970a85e392d19fadb494f447fb64a18f6c0d9b7205100d66c0e9c39ec5a75ac) 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.

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

Malicious code in httpinfrastructure (npm) Source: ghsa-malware (34c25bae800f5d8e992b1fbda3daf30b45b483169d38d39cd5f87d0d3be3953c) 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.

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

Malicious code in panel-farm (npm) Source: ghsa-malware (f0fb84873025b1118cd30fa3e2ab254bce810b9e114d1114fa49d2b26b25720c) 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.

Malicious code in noblox.js-proxies (npm) Source: ghsa-malware (96f75d109d6a7cc619d93e3a635cd1c1da7eceb5f8131f91e909c241e7c78cfc) 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.

The code exhibits potential security risks due to the handling of sensitive user credentials and lack of proper error handling. The risk score reflects the potential for sensitive data exposure. The malware score indicates a possibility of malicious behavior if the code is misused, particularly in how it handles user login information.

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

Malicious code in fflask (PyPI)

Live on PyPI for 11 hours and 23 minutes before removal. Socket users were protected even while the package was live.

The code is designed to collect detailed system and user information and transmit it to external servers without user consent. This behavior is consistent with data exfiltration and poses a significant privacy risk.

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

Malicious code in gc-gsl-editor (npm) Source: ghsa-malware (7a4adc0fa0f46c847c26f536f6d3390e092f77b6f9a533eaab32b95b5cf83499) 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.

The code is vulnerable to command injection and can be exploited by an attacker to run malicious commands on the system. It poses a high security risk and should be revised to include proper input validation and sanitization.

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

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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.

Malicious code in protobufjs-databricks (npm) Source: ghsa-malware (2ae198b4c60528a62453f589485b597ef1cfc87e25d9af4500e8445aac5b5c3b) 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.

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

Malicious code in mineflayer-patcher (npm) Source: ghsa-malware (5249a1e663bcc7ec837346cbcd549a3e0e2af0039ffd68a532f043c025ec119f) 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.

The code appears highly obfuscated with the use of eval() indicating a potential for malicious behavior by executing arbitrary code. The obscured operations and presence of timing functions hint at suspicious activity. Although specific malicious actions are not immediately clear due to the obfuscation, the usage patterns are typical of attempts to conceal harmful operations.

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

Malicious code in ada-balance-adapter (npm) Source: ghsa-malware (6727c4df16febb1399cae1caa5604a2441a91be359ed453d105095de36d6bb03) 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.

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

Malicious code in bablpluginsyntaxdynamicimport (npm) Source: ghsa-malware (c59572f2bc92d923ebe87aeee4cc1ccb84e1e60c29e5f6fbe6a0ca8bda407b8b) 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.

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

Malicious code in rsckjs (npm) Source: ghsa-malware (69f23056f72baffbfb6139e3adde702c967658886c92a25fa97dc8ff30ded12c) 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.

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

Malicious code in orbit-tracking (npm) Source: ghsa-malware (b514c540f5d1347c7573a09c60655ff0d5981f14a3e86f7d0bfe30316c2e2894) 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.

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

Malicious code in phpmyadmin (npm) Source: ghsa-malware (1554572f62f66f781c39beac2b19170401216f0d4d9a828358a89793b7fdcc46) 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.

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

The code exhibits potential security risks related to user authentication and data handling, particularly with the CAPTCHA cracking functionality. While there are no clear indicators of malware, the use of external libraries and dynamic code execution raises concerns. The overall risk is moderate, and further scrutiny is recommended.

Malicious code in pp-amount-field (npm) Source: ghsa-malware (25fda0186ce26a0871fe78f3ec99900b6d2f42baa4d4ecb6ea1590d3076b8386) 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.

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

Malicious code in signup-ui-core (npm) Source: ghsa-malware (5efd0acaccf47da92b3f4cb09e80de3b56ec88952a48030330e28d308b983e36) 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.

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

Malicious code in constantparam (npm) Source: ghsa-malware (d70c96d26cc546890595df8beea2035e8d6a30089ede37bc41acbaa37f2a9186) 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.

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

Malicious code in lolo1122 (npm) Source: ghsa-malware (42db12ae19e91064867283ce996f4b0e498f5633f088a0d8eeb3459c024dfa8c) 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.

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

Malicious code in share-client (npm) Source: ghsa-malware (ba664ab24090b0fcbea9d3c7c58134f47472535eba4ff9d4a65946aa5efad8ed) 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.

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

Malicious code in eosio-signer (PyPI)

Live on PyPI for 14 hours and 52 minutes before removal. Socket users were protected even while the package was live.

Malicious code in iotspaces (npm) Source: ghsa-malware (9970a85e392d19fadb494f447fb64a18f6c0d9b7205100d66c0e9c39ec5a75ac) 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.

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

Malicious code in httpinfrastructure (npm) Source: ghsa-malware (34c25bae800f5d8e992b1fbda3daf30b45b483169d38d39cd5f87d0d3be3953c) 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.

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

Malicious code in panel-farm (npm) Source: ghsa-malware (f0fb84873025b1118cd30fa3e2ab254bce810b9e114d1114fa49d2b26b25720c) 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.

Malicious code in noblox.js-proxies (npm) Source: ghsa-malware (96f75d109d6a7cc619d93e3a635cd1c1da7eceb5f8131f91e909c241e7c78cfc) 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.

The code exhibits potential security risks due to the handling of sensitive user credentials and lack of proper error handling. The risk score reflects the potential for sensitive data exposure. The malware score indicates a possibility of malicious behavior if the code is misused, particularly in how it handles user login information.

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

Malicious code in fflask (PyPI)

Live on PyPI for 11 hours and 23 minutes before removal. Socket users were protected even while the package was live.

The code is designed to collect detailed system and user information and transmit it to external servers without user consent. This behavior is consistent with data exfiltration and poses a significant privacy risk.

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

Malicious code in gc-gsl-editor (npm) Source: ghsa-malware (7a4adc0fa0f46c847c26f536f6d3390e092f77b6f9a533eaab32b95b5cf83499) 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.

The code is vulnerable to command injection and can be exploited by an attacker to run malicious commands on the system. It poses a high security risk and should be revised to include proper input validation and sanitization.

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

Malicious code in brave-core (npm) Source: ghsa-malware (64124298f67bb4effd7c57f151d40e754666278b542f85d9f4f78b80309c5201) 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.

Malicious code in protobufjs-databricks (npm) Source: ghsa-malware (2ae198b4c60528a62453f589485b597ef1cfc87e25d9af4500e8445aac5b5c3b) 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.

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

Malicious code in mineflayer-patcher (npm) Source: ghsa-malware (5249a1e663bcc7ec837346cbcd549a3e0e2af0039ffd68a532f043c025ec119f) 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.

The code appears highly obfuscated with the use of eval() indicating a potential for malicious behavior by executing arbitrary code. The obscured operations and presence of timing functions hint at suspicious activity. Although specific malicious actions are not immediately clear due to the obfuscation, the usage patterns are typical of attempts to conceal harmful operations.

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

Malicious code in ada-balance-adapter (npm) Source: ghsa-malware (6727c4df16febb1399cae1caa5604a2441a91be359ed453d105095de36d6bb03) 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.

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

Malicious code in bablpluginsyntaxdynamicimport (npm) Source: ghsa-malware (c59572f2bc92d923ebe87aeee4cc1ccb84e1e60c29e5f6fbe6a0ca8bda407b8b) 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.

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

Malicious code in rsckjs (npm) Source: ghsa-malware (69f23056f72baffbfb6139e3adde702c967658886c92a25fa97dc8ff30ded12c) 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.

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