Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @servicetitan/intl

The npm package @servicetitan/intl was compromised and distributed with malware. Systems with the package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the malicious package installed
Ecosystems
Attack vectors
Affected entities
  • @servicetitan/intlnpm package containing malware

The npm package @servicetitan/intl was found to contain malware. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised, indicating the malware grants broad system access to an outside entity.\n\nThe advisory recommends immediate removal of the package and rotation of all secrets and keys from a different, uncompromised computer. However, it notes that full removal of all malicious software cannot be guaranteed due to the level of access the malware may have obtained.\n\nThe incident was disclosed on 2026-08-04 via GitHub's advisory system.

Indicators of compromise

Packages
  • @servicetitan/intl

Remediation

  • Immediately remove the @servicetitan/intl package from all affected systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Conduct a full security audit of any system that had the package installed
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Review package installation logs to identify all systems and timeframes affected
  • Consider full system reimaging if the package was installed on critical infrastructure

Sources

  1. GitHub Advisory GHSA-px4p-f5xc-8733 · GitHub Advisory Database

Cite this entry

"Malware in @servicetitan/intl." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-servicetitan-intl-1udlta

Suggest a correction

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

  1. containedcritical

    Malware in fetch-runtime

    Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  2. resolvedcritical

    Malicious code in ghazaly (npm)

    The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.

    npmCompromised packageDependency confusion
  3. containedcritical

    Malicious code in base65-13x (npm)

    base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.

    npmCompromised package
  4. containedcritical

    Malicious code in kit-vim-map (npm)

    The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.

    npmCompromised packageMalicious commit