Socket
Book a DemoInstallSign in
Socket

Secure your dependencies. Ship with confidence.

Socket is a developer-first security platform that protects your code from both vulnerable and malicious dependencies.

Install GitHub AppBook a Demo

Find and compare millions of open source packages

Quickly evaluate the security and health of any open source package.

jquery
t

timmywil published 3.7.1

left-pad
s

stevemao published 1.3.0

react
r

react-bot published 19.2.3

We protect you from vulnerable and malicious packages

@paraspace-liquidator/utils

0.1.62

by rjman-ljm

Live on npm

Blocked by Socket

High-risk due to embedded private keys and API credentials spread across multi-network configurations, coupled with runtime prompts for secrets and broad external dependencies. Immediate remediation should remove all hardcoded secrets, implement secure secret management (environment variables with strict permissions, vaults, or CI/CD secret stores), enforce least-privilege signer creation, and audit all external endpoints. This codebase presents a significant supply-chain risk and potential for unauthorized signing or data exfiltration if deployed as-is.

meutils

2024.8.1.9.42.18

Live on PyPI

Blocked by Socket

The code sends sensitive credentials from environment variables over an unencrypted HTTP connection to an external API service at api[.]sqhyw[.]net:90. It authenticates using username/password from the YEZI_USER environment variable, retrieves access tokens, and automates the process of obtaining mobile phone numbers and SMS verification codes. This behavior poses significant supply chain security risks through: (1) leakage of environment variable credentials over unencrypted HTTP, (2) interaction with a suspicious external domain on a non-standard port, (3) logging of potentially sensitive API responses including tokens and SMS codes, and (4) facilitation of SMS verification bypass which could enable fraudulent account creation or spam activities. The code continuously polls the external API for up to 120 seconds to retrieve SMS codes, creating additional operational risks. While not containing traditional malware payloads, the credential exfiltration and suspicious external communication patterns justify classification as malware due to the significant security risks posed to systems that deploy this code.

nyc-config

4.1.0

by jpdtestjpd

Live on npm

Blocked by Socket

The code is highly suspicious due to its collection and transmission of system information to external servers without user consent. The use of hardcoded IP addresses and fallback mechanisms for data transmission indicates potential malicious intent.

yxspkg

6.9.6

Live on PyPI

Blocked by Socket

The fragment is an opaque, binary/packed payload or heavily obfuscated content that cannot be reliably analyzed statically. While this alone does not prove malicious intent, it signals high risk and warrants isolation, request for a readable source or deobfuscated form, and controlled dynamic analysis to determine any harmful behavior or data leakage potential.

alita-sdk

0.3.422

Live on PyPI

Blocked by Socket

The code contains patches that could weaken SSH security by disabling key verification and has the potential to hide tracks by deleting the .git directory. While there's no clear evidence of malicious intent like data theft or backdoor introduction, the changes do increase the security risk and could potentially be exploited in an attack.

md-progress-circular

30000.0.0

by rayanlecat

Removed from npm

Blocked by Socket

The code is malicious as it collects and transmits sensitive user and system data to an external server without consent. This poses a significant security risk.

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

github.com/tensilick/gopostexploit

v0.0.0-20240117073008-8475bc031194

Live on Go Modules

Blocked by Socket

This code implements a straightforward reverse SSH TCP tunnel that exposes local services to a remote SSH peer and allows local data to be forwarded to that peer. The implementation itself is not obfuscated and contains no hard-coded credentials, but in the context of an implant package it is consistent with backdoor/tunneling behavior and represents a significant security risk. Recommend treating this component as malicious or high-risk unless its presence is explicitly required and audited; if used legitimately, add access controls, authentication, and stricter logging/visibility to reduce abuse potential.

cbre-flow-common

99.2.0

Live on npm

Blocked by Socket

This code is malicious and implements a covert data-collection and exfiltration mechanism. It gathers local system identifiers and the host public IP, hex-encodes them, and transmits the encoded payload to an attacker-controlled domain via DNS queries while also contacting ifconfig.me. Treat this as a compromise/supply-chain backdoor: do not execute, remove from any codebase, and investigate any systems that ran it.

cookiesgetr

0.1.0

Removed from PyPI

Blocked by Socket

The code is malicious as it involves unauthorized data exfiltration by sending session cookies to an external server. This poses a significant security risk.

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

@bootstrap-base-managed-designs/bootstrap-nabtraderedesign

4.999.999

Removed from npm

Blocked by Socket

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

cgse-core

2025.0.8

Removed from PyPI

Blocked by Socket

This module is a logging control server that tolerates remote control and remote log ingestion. The code contains a severe unsafe-deserialization vulnerability: it unpickles data directly from ZMQ sockets (commander and receiver). An attacker able to connect to those sockets can execute arbitrary code via crafted pickle payloads and/or control the logging server (quit/roll/set_level). Additionally, logs are forwarded to a remote textualog endpoint which could leak sensitive information. No obfuscation or explicit malicious payloads are present, but the deserialization pattern and lack of authentication make this code high-risk for remote exploitation and potential supply-chain abuse. Recommend replacing pickle with a safe serialization format (JSON, msgpack with safe types), adding authentication/authorization for command sockets, validating inputs, and auditing what data is logged and forwarded to remote hosts.

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

smartchart

6.9.3

Live on PyPI

Blocked by Socket

This module intentionally embeds and executes hidden LZMA+base64 payloads at import time. That pattern (immediate exec of compressed/encoded blobs and opaque function calls) is highly suspicious and consistent with obfuscation and potential malicious/supply-chain behavior. Treat this file as high risk: do not run or import it in trusted environments. Decompress and audit both payloads in a secure, isolated sandbox before any use.

cronapp-lib-js

4.1.5

by cronapp

Live on npm

Blocked by Socket

High risk: the code demonstrates an obfuscated dynamic loader capable of reconstructing and executing arbitrary code at runtime across both Node and browser environments. This is a classic indicator of a potential backdoor or supply-chain dropper. Such patterns should not be trusted in open-source dependencies without rigorous provenance verification, deobfuscation, and signing. Removal or replacement with vetted components is advised.

ncert-learn

5.3.0

Live on PyPI

Blocked by Socket

This script invokes xmrig.exe to perform a cryptomining benchmark using the --bench=1M and --submit parameters, potentially submitting results over the network. Unauthorized execution can consume system resources for mining and send data externally without user consent, making it a malicious threat.

esoftplay

0.0.96-r

by danang

Live on npm

Blocked by Socket

This file contains an explicit data exfiltration channel: tm() sends project configuration and dependency details to a hardcoded Telegram bot token and chat_id using curl invoked via shell exec. Combined with unescaped string concatenation into shell commands (command injection risk) and use of child_process.exec throughout, this is a significant supply-chain/privacy risk. Remediation: remove or disable tm(), remove hardcoded tokens, make telemetry optional and configurable, avoid child_process.exec with shell and prefer spawn/execFile with argument arrays or properly escape inputs, and sanitize any data used in shell contexts. Treat this module as unsafe for inclusion until those issues are fixed.

testpalm-api

0.13.2

by meow-test

Removed from npm

Blocked by Socket

The script is designed to send telemetry data to a remote server, which poses a significant security risk due to the potential exposure of sensitive information.

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

ailever

0.2.656

Live on PyPI

Blocked by Socket

The code presents a strong supply-chain and remote-execution risk by automatically downloading and executing remote Python payloads without integrity checks or sandboxing. It also creates and runs external services (Jupyter, Visdom, RStudio) based on user inputs, which can amplify impact if the remote payload is malicious. Mitigations include removing remote code execution paths, adding cryptographic verification (signatures or hash checks), isolating execution (sandboxes or containerization), validating inputs, and avoiding untrusted downloads or executions.

poc-lelouch

1.8.0

by virgulino.silva

Removed from npm

Blocked by Socket

The script is designed to send sensitive environment variable data to an external server, which is a clear indication of malicious behavior.

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

yxspkg

6.10.28

Live on PyPI

Blocked by Socket

The fragment is an opaque, binary/packed payload or heavily obfuscated content that cannot be reliably analyzed statically. While this alone does not prove malicious intent, it signals high risk and warrants isolation, request for a readable source or deobfuscated form, and controlled dynamic analysis to determine any harmful behavior or data leakage potential.

pix-xui

2.51.2

by evyzkbhjdu

Removed from npm

Blocked by Socket

The code is a classic reverse shell implementation, posing a significant security risk by allowing remote command execution on the host system. This behavior is indicative of malicious intent.

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

mtmai

0.3.1382

Live on PyPI

Blocked by Socket

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.

cloudsplaining

4.4.5

by parthu1211

Removed from npm

Blocked by Socket

This script is highly suspicious and likely malicious as it attempts to exfiltrate sensitive information from the system to a remote server.

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

hiphp

0.2.29

Live on PyPI

Blocked by Socket

The provided code fragment contains an embedded PHP payload designed to enumerate server files, package them into a zip, read and base64-encode the archive, and output it along with extensive server environment information. This is strongly indicative of a webshell or data-exfiltration backdoor. Even though the Python wrapper is syntactically broken and the PHP has small syntax issues (possibly due to truncation), the operational intent is clear and malicious. Treat any occurrence of this payload in a package as high risk: remove the code, investigate how it arrived, search for written PHP files on web roots, and consider rotating credentials and performing a full compromise assessment.

c2-ddos-del

1.0.9

by nekonekomon

Live on npm

Blocked by Socket

This package modifies user shell startup files without consent and injects a token that will be executed by future shells. That behavior is unexpected for most packages and can be used as a persistence/backdoor mechanism. Even if the injected string is benign in the package's intended context, altering ~/.bashrc or ~/.zshrc silently is a high-risk action and should be treated as malicious or at least unacceptable for a trusted package. Recommend not using this package and removing injected lines from user rc files.

cavern-piano-drz718

1.0.0

by afifaljafari112

Removed from npm

Blocked by Socket

The code imports several external libraries with non-standard names and calls a method 'functame' on each. The behavior and purpose of 'functame' are unclear, and the code does not perform any meaningful operations. Given the anomalies and lack of clear intent, further investigation of the external libraries is recommended. However, there is no direct evidence of malicious activity in this fragment itself.

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

@paraspace-liquidator/utils

0.1.62

by rjman-ljm

Live on npm

Blocked by Socket

High-risk due to embedded private keys and API credentials spread across multi-network configurations, coupled with runtime prompts for secrets and broad external dependencies. Immediate remediation should remove all hardcoded secrets, implement secure secret management (environment variables with strict permissions, vaults, or CI/CD secret stores), enforce least-privilege signer creation, and audit all external endpoints. This codebase presents a significant supply-chain risk and potential for unauthorized signing or data exfiltration if deployed as-is.

meutils

2024.8.1.9.42.18

Live on PyPI

Blocked by Socket

The code sends sensitive credentials from environment variables over an unencrypted HTTP connection to an external API service at api[.]sqhyw[.]net:90. It authenticates using username/password from the YEZI_USER environment variable, retrieves access tokens, and automates the process of obtaining mobile phone numbers and SMS verification codes. This behavior poses significant supply chain security risks through: (1) leakage of environment variable credentials over unencrypted HTTP, (2) interaction with a suspicious external domain on a non-standard port, (3) logging of potentially sensitive API responses including tokens and SMS codes, and (4) facilitation of SMS verification bypass which could enable fraudulent account creation or spam activities. The code continuously polls the external API for up to 120 seconds to retrieve SMS codes, creating additional operational risks. While not containing traditional malware payloads, the credential exfiltration and suspicious external communication patterns justify classification as malware due to the significant security risks posed to systems that deploy this code.

nyc-config

4.1.0

by jpdtestjpd

Live on npm

Blocked by Socket

The code is highly suspicious due to its collection and transmission of system information to external servers without user consent. The use of hardcoded IP addresses and fallback mechanisms for data transmission indicates potential malicious intent.

yxspkg

6.9.6

Live on PyPI

Blocked by Socket

The fragment is an opaque, binary/packed payload or heavily obfuscated content that cannot be reliably analyzed statically. While this alone does not prove malicious intent, it signals high risk and warrants isolation, request for a readable source or deobfuscated form, and controlled dynamic analysis to determine any harmful behavior or data leakage potential.

alita-sdk

0.3.422

Live on PyPI

Blocked by Socket

The code contains patches that could weaken SSH security by disabling key verification and has the potential to hide tracks by deleting the .git directory. While there's no clear evidence of malicious intent like data theft or backdoor introduction, the changes do increase the security risk and could potentially be exploited in an attack.

md-progress-circular

30000.0.0

by rayanlecat

Removed from npm

Blocked by Socket

The code is malicious as it collects and transmits sensitive user and system data to an external server without consent. This poses a significant security risk.

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

github.com/tensilick/gopostexploit

v0.0.0-20240117073008-8475bc031194

Live on Go Modules

Blocked by Socket

This code implements a straightforward reverse SSH TCP tunnel that exposes local services to a remote SSH peer and allows local data to be forwarded to that peer. The implementation itself is not obfuscated and contains no hard-coded credentials, but in the context of an implant package it is consistent with backdoor/tunneling behavior and represents a significant security risk. Recommend treating this component as malicious or high-risk unless its presence is explicitly required and audited; if used legitimately, add access controls, authentication, and stricter logging/visibility to reduce abuse potential.

cbre-flow-common

99.2.0

Live on npm

Blocked by Socket

This code is malicious and implements a covert data-collection and exfiltration mechanism. It gathers local system identifiers and the host public IP, hex-encodes them, and transmits the encoded payload to an attacker-controlled domain via DNS queries while also contacting ifconfig.me. Treat this as a compromise/supply-chain backdoor: do not execute, remove from any codebase, and investigate any systems that ran it.

cookiesgetr

0.1.0

Removed from PyPI

Blocked by Socket

The code is malicious as it involves unauthorized data exfiltration by sending session cookies to an external server. This poses a significant security risk.

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

@bootstrap-base-managed-designs/bootstrap-nabtraderedesign

4.999.999

Removed from npm

Blocked by Socket

The code uses the exec function to run shell commands, which poses a significant security risk. It could potentially execute malicious code if the input to exec is manipulated. Redirecting output to /dev/null to hide execution details is suspicious.

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

cgse-core

2025.0.8

Removed from PyPI

Blocked by Socket

This module is a logging control server that tolerates remote control and remote log ingestion. The code contains a severe unsafe-deserialization vulnerability: it unpickles data directly from ZMQ sockets (commander and receiver). An attacker able to connect to those sockets can execute arbitrary code via crafted pickle payloads and/or control the logging server (quit/roll/set_level). Additionally, logs are forwarded to a remote textualog endpoint which could leak sensitive information. No obfuscation or explicit malicious payloads are present, but the deserialization pattern and lack of authentication make this code high-risk for remote exploitation and potential supply-chain abuse. Recommend replacing pickle with a safe serialization format (JSON, msgpack with safe types), adding authentication/authorization for command sockets, validating inputs, and auditing what data is logged and forwarded to remote hosts.

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

smartchart

6.9.3

Live on PyPI

Blocked by Socket

This module intentionally embeds and executes hidden LZMA+base64 payloads at import time. That pattern (immediate exec of compressed/encoded blobs and opaque function calls) is highly suspicious and consistent with obfuscation and potential malicious/supply-chain behavior. Treat this file as high risk: do not run or import it in trusted environments. Decompress and audit both payloads in a secure, isolated sandbox before any use.

cronapp-lib-js

4.1.5

by cronapp

Live on npm

Blocked by Socket

High risk: the code demonstrates an obfuscated dynamic loader capable of reconstructing and executing arbitrary code at runtime across both Node and browser environments. This is a classic indicator of a potential backdoor or supply-chain dropper. Such patterns should not be trusted in open-source dependencies without rigorous provenance verification, deobfuscation, and signing. Removal or replacement with vetted components is advised.

ncert-learn

5.3.0

Live on PyPI

Blocked by Socket

This script invokes xmrig.exe to perform a cryptomining benchmark using the --bench=1M and --submit parameters, potentially submitting results over the network. Unauthorized execution can consume system resources for mining and send data externally without user consent, making it a malicious threat.

esoftplay

0.0.96-r

by danang

Live on npm

Blocked by Socket

This file contains an explicit data exfiltration channel: tm() sends project configuration and dependency details to a hardcoded Telegram bot token and chat_id using curl invoked via shell exec. Combined with unescaped string concatenation into shell commands (command injection risk) and use of child_process.exec throughout, this is a significant supply-chain/privacy risk. Remediation: remove or disable tm(), remove hardcoded tokens, make telemetry optional and configurable, avoid child_process.exec with shell and prefer spawn/execFile with argument arrays or properly escape inputs, and sanitize any data used in shell contexts. Treat this module as unsafe for inclusion until those issues are fixed.

testpalm-api

0.13.2

by meow-test

Removed from npm

Blocked by Socket

The script is designed to send telemetry data to a remote server, which poses a significant security risk due to the potential exposure of sensitive information.

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

ailever

0.2.656

Live on PyPI

Blocked by Socket

The code presents a strong supply-chain and remote-execution risk by automatically downloading and executing remote Python payloads without integrity checks or sandboxing. It also creates and runs external services (Jupyter, Visdom, RStudio) based on user inputs, which can amplify impact if the remote payload is malicious. Mitigations include removing remote code execution paths, adding cryptographic verification (signatures or hash checks), isolating execution (sandboxes or containerization), validating inputs, and avoiding untrusted downloads or executions.

poc-lelouch

1.8.0

by virgulino.silva

Removed from npm

Blocked by Socket

The script is designed to send sensitive environment variable data to an external server, which is a clear indication of malicious behavior.

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

yxspkg

6.10.28

Live on PyPI

Blocked by Socket

The fragment is an opaque, binary/packed payload or heavily obfuscated content that cannot be reliably analyzed statically. While this alone does not prove malicious intent, it signals high risk and warrants isolation, request for a readable source or deobfuscated form, and controlled dynamic analysis to determine any harmful behavior or data leakage potential.

pix-xui

2.51.2

by evyzkbhjdu

Removed from npm

Blocked by Socket

The code is a classic reverse shell implementation, posing a significant security risk by allowing remote command execution on the host system. This behavior is indicative of malicious intent.

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

mtmai

0.3.1382

Live on PyPI

Blocked by Socket

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.

cloudsplaining

4.4.5

by parthu1211

Removed from npm

Blocked by Socket

This script is highly suspicious and likely malicious as it attempts to exfiltrate sensitive information from the system to a remote server.

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

hiphp

0.2.29

Live on PyPI

Blocked by Socket

The provided code fragment contains an embedded PHP payload designed to enumerate server files, package them into a zip, read and base64-encode the archive, and output it along with extensive server environment information. This is strongly indicative of a webshell or data-exfiltration backdoor. Even though the Python wrapper is syntactically broken and the PHP has small syntax issues (possibly due to truncation), the operational intent is clear and malicious. Treat any occurrence of this payload in a package as high risk: remove the code, investigate how it arrived, search for written PHP files on web roots, and consider rotating credentials and performing a full compromise assessment.

c2-ddos-del

1.0.9

by nekonekomon

Live on npm

Blocked by Socket

This package modifies user shell startup files without consent and injects a token that will be executed by future shells. That behavior is unexpected for most packages and can be used as a persistence/backdoor mechanism. Even if the injected string is benign in the package's intended context, altering ~/.bashrc or ~/.zshrc silently is a high-risk action and should be treated as malicious or at least unacceptable for a trusted package. Recommend not using this package and removing injected lines from user rc files.

cavern-piano-drz718

1.0.0

by afifaljafari112

Removed from npm

Blocked by Socket

The code imports several external libraries with non-standard names and calls a method 'functame' on each. The behavior and purpose of 'functame' are unclear, and the code does not perform any meaningful operations. Given the anomalies and lack of clear intent, further investigation of the external libraries is recommended. However, there is no direct evidence of malicious activity in this fragment itself.

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

Detect and block software supply chain attacks

Socket detects traditional vulnerabilities (CVEs) but goes beyond that to scan the actual code of dependencies for malicious behavior. It proactively detects and blocks 70+ signals of supply chain risk in open source code, for comprehensive protection.

Possible typosquat attack

Known malware

Suspicious Stars on GitHub

HTTP dependency

Git dependency

GitHub dependency

AI-detected potential malware

Obfuscated code

Telemetry

Protestware or potentially unwanted behavior

42 more alerts

Detect suspicious package updates in real-time

Socket detects and blocks malicious dependencies, often within just minutes of them being published to public registries, making it the most effective tool for blocking zero-day supply chain attacks.

GitHub app screenshot

Developers love Socket

Socket is built by a team of prolific open source maintainers whose software is downloaded over 1 billion times per month. We understand how to build tools that developers love. But don’t take our word for it.

Even more developer love
Install GitHub AppRead the docs

Security teams trust Socket

The best security teams in the world use Socket to get visibility into supply chain risk, and to build a security feedback loop into the development process.

Even more security team love
Book a DemoRead the blog

Why teams choose Socket

Pro-active security

Depend on Socket to prevent malicious open source dependencies from infiltrating your app.

Easy to install

Install the Socket GitHub App in just 2 clicks and get protected today.

Comprehensive open source protection

Block 70+ issues in open source code, including malware, typo-squatting, hidden code, misleading packages, permission creep, and more.

Develop faster

Reduce work by surfacing actionable security information directly in GitHub. Empower developers to make better decisions.

Supply chain attacks are on the rise

Attackers have taken notice of the opportunity to attack organizations through open source dependencies. Supply chain attacks rose a whopping 700% in the past year, with over 15,000 recorded attacks.

Nov 23, 2025

Shai Hulud v2

Shai Hulud v2 campaign: preinstall script (setup_bun.js) and loader (setup_bin.js) that installs/locates Bun and executes an obfuscated bundled malicious script (bun_environment.js) with suppressed output.

Nov 05, 2025

Elves on npm

A surge of auto-generated "elf-stats" npm packages is being published every two minutes from new accounts. These packages contain simple malware variants and are being rapidly removed by npm. At least 420 unique packages have been identified, often described as being generated every two minutes, with some mentioning a capture the flag challenge or test.

Jul 04, 2025

RubyGems Automation-Tool Infostealer

Since at least March 2023, a threat actor using multiple aliases uploaded 60 malicious gems to RubyGems that masquerade as automation tools (Instagram, TikTok, Twitter, Telegram, WordPress, and Naver). The gems display a Korean Glimmer-DSL-LibUI login window, then exfiltrate the entered username/password and the host's MAC address via HTTP POST to threat actor-controlled infrastructure.

Mar 13, 2025

North Korea's Contagious Interview Campaign

Since late 2024, we have tracked hundreds of malicious npm packages and supporting infrastructure tied to North Korea's Contagious Interview operation, with tens of thousands of downloads targeting developers and tech job seekers. The threat actors run a factory-style playbook: recruiter lures and fake coding tests, polished GitHub templates, and typosquatted or deceptive dependencies that install or import into real projects.

Jul 23, 2024

Network Reconnaissance Campaign

A malicious npm supply chain attack that leveraged 60 packages across three disposable npm accounts to fingerprint developer workstations and CI/CD servers during installation. Each package embedded a compact postinstall script that collected hostnames, internal and external IP addresses, DNS resolvers, usernames, home and working directories, and package metadata, then exfiltrated this data as a JSON blob to a hardcoded Discord webhook.

Ready to dive in?

Get protected by Socket with just 2 clicks.

Install GitHub AppBook a Demo

The latest from the Socket team

Get our latest security research, open source insights, and product updates.

View all articles