Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in @sarex-team/ui-kit (npm)

@sarex-team/ui-kit, an npm package, contained malicious code that exfiltrated host identity (OS username, hostname, working directory) via DNS queries to oob.sl4x0.xyz during installation and on require(). The package used obfuscation to evade detection and presented itself as enterprise utilities.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
All npm users who installed @sarex-team/ui-kit
Ecosystems
Attack vectors
Affected entities
  • @sarex-team/ui-kit

@sarex-team/ui-kit is a malicious npm package that executes exfiltration code both at install time (via package.json scripts.install) and at runtime (via top-level require in lib/core.js). The malicious code collects sensitive host information including the installer's OS username, hostname, and current working directory basename, then performs DNS lookups against subdomains of oob.sl4x0.xyz constructed from these values to leak host identity through DNS queries.\n\nThe package employed obfuscation techniques to evade static analysis, reconstructing sensitive API names and the destination domain at runtime from hex character-code arrays using obfuscator.io-style identifiers. The package falsely presented itself as "Enterprise-grade utilities" with decoy modules for validation, formatting, networking, cryptography, and async operations.\n\nThe package's metadata contained indicators of malicious intent: the homepage and repository URL (github.com/slaxorg/@sarex-team/ui-kit) was malformed and did not resolve to a real repository, and the author email (research@sl4x0.xyz) matched the exfiltration domain, suggesting coordinated malicious activity.\n\nThe incident was identified and reported through the OpenSSF malicious packages repository, with the package now flagged in security advisories.", <parameter name="remediation">["Immediately uninstall @sarex-team/ui-kit from all systems", "Audit npm install logs to identify when the package was installed and on which systems", "Assume compromise of any system that installed this package; rotate credentials and review for unauthorized access", "Check for DNS queries to oob.sl4x0.xyz or related subdomains in network logs", "Review npm audit and lock files to ensure no other malicious packages are present", "Use npm security tools to scan for similar obfuscated malicious packages", "Report any systems that installed this package to your security team for forensic analysis"]

Indicators of compromise

Packages
  • @sarex-team/ui-kit
Domains
  • oob.sl4x0.xyz
  • sl4x0.xyz

Remediation

  • Review the linked advisory; remove or upgrade the affected component and rotate any exposed credentials.

Sources

  1. GitHub Advisory GHSA-jj24-637c-qxch · GitHub Advisory Database

Cite this entry

"Malicious code in @sarex-team/ui-kit (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malicious-code-in-sarex-team-ui-kit-npm-16fmjy

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package