Supply chain · rust · High

Malicious Rust Package 'semantic-search-client' Identified in crates.io

Threat Engine Auto-Feed · data current as of 2026-07-19

A critical severity malicious package, 'semantic-search-client' version 99.0.1, has been identified in the Rust ecosystem's crates.io. This package communicates with malicious domains and executes malicious commands, posing a significant supply-chain risk to projects that integrated it.

  • Package: rust / semantic-search-client
  • Affected versions: = 99.0.1
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Malicious package

The OpenSSF Package Analysis project identified 'semantic-search-client' version 99.0.1 on crates.io as malicious. The package was flagged due to its communication with a domain associated with malicious activity and the execution of commands linked to malicious behavior.

How the attack works

This is a malicious package attack where an attacker publishes a seemingly legitimate software component containing hidden malicious code. When developers integrate this package into their projects, the malicious code is introduced into their build environment or deployed applications. The attack leverages the trust placed in public package repositories to distribute harmful capabilities, such as establishing external communications or executing unauthorized commands.

Who's exposed

Profiles most at risk

  • Development teams using the Rust ecosystem
  • Organizations whose CI/CD pipelines automatically pull the latest versions of dependencies
  • Projects that directly or indirectly depend on 'semantic-search-client' version 99.0.1

Conditions that increase exposure

  • Unpinned dependencies that allow automatic updates to vulnerable versions
  • Lack of dependency lockfiles or infrequent updates of lockfiles
  • Use of internal package mirrors that may not filter out malicious packages
  • Build environments with broad network access

Blast-radius scenarios

  • If installed, an attacker could establish outbound connections from the build environment or deployed application to a malicious command-and-control server.
  • The package could execute arbitrary commands within the context of the build process or the runtime environment, potentially leading to data exfiltration, system compromise, or further lateral movement.
  • The blast radius extends to any system or application where the affected version of 'semantic-search-client' is compiled or run.

What to do (defensive)

Detect

  • Scan dependency trees for 'semantic-search-client' version 99.0.1.
  • Monitor network traffic from build environments and applications for suspicious outbound connections to unknown or malicious domains.
  • Review build logs and system logs for unexpected command executions originating from package installation or application runtime.

Contain

  • Immediately quarantine or remove any systems or applications found to be running or built with 'semantic-search-client' version 99.0.1.
  • Block network access to known malicious domains associated with this package from all development and production environments.
  • Isolate build environments that may have processed the malicious package.

Remediate

  • Remove 'semantic-search-client' version 99.0.1 from all project dependencies.
  • Update dependency management configurations to pin versions and utilize lockfiles to prevent automatic inclusion of malicious versions.
  • Rebuild all affected applications and systems from a clean, verified state after removing the malicious dependency.
  • Conduct a thorough security audit of any systems that may have been compromised by the package to identify and remove any persistent threats.

Frontier verdict — High

Prioritize immediate detection and removal of 'semantic-search-client' version 99.0.1 due to its critical severity and confirmed malicious behavior.

Sources

For detection-engineering and awareness only · point-in-time · not security advice · sourced from the GitHub Advisory Database.