Malicious code in triage_bot_using_sdkv3 (npm)
The npm package triage_bot_using_sdkv3 contained malicious code that executed during installation, exfiltrating system information and local files to an attacker-controlled endpoint. The package registered a preinstall hook that collected hostname, user information, DNS configuration, and sensitive files like /etc/passwd and /etc/hosts.
- Disclosed
- Last updated
- Blast radius
- Any developer or system that installed triage_bot_using_sdkv3 via npm install
- Ecosystems
- Attack vectors
- Affected entities
- triage_bot_using_sdkv3npm package containing malicious preinstall hook
The npm package triage_bot_using_sdkv3 was found to contain malicious code that executed automatically during package installation. The package.json file registered a preinstall hook that ran index.js when npm install was executed.
The malicious index.js script collected sensitive system information including the system hostname, user account details via os.userInfo(), home directory path, and DNS server configuration. It also read local system files /etc/passwd and /etc/hosts using fs.readFileSync.
All collected data was then exfiltrated via HTTPS POST requests to a hardcoded Burp Collaborator subdomain (mh7rhchf58lgymyr9wffhwfprgx7lx9m.oastify.com), an attacker-controlled out-of-band endpoint. This means any developer or system performing a default npm install of this package would have their host identifiers and local account/host configuration transmitted to the attacker.
The malicious package was identified and reported by the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- triage_bot_using_sdkv3
- Domains
- mh7rhchf58lgymyr9wffhwfprgx7lx9m.oastify.com
Remediation
- Immediately uninstall triage_bot_using_sdkv3 from all systems where it was installed
- Review npm install logs and audit systems that may have installed this package for signs of compromise
- Change credentials and review account activity on any systems that installed the package
- Monitor the exfiltration endpoint mh7rhchf58lgymyr9wffhwfprgx7lx9m.oastify.com for any data that may have been transmitted
- Use npm audit to check for this package in dependency trees and remove it
- Consider implementing npm package scanning and verification in your CI/CD pipeline
Sources
- GitHub Advisory GHSA-8pwc-32rm-4cgm · GitHub Advisory Database
Cite this entry
"Malicious code in triage_bot_using_sdkv3 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 28, 2026; last updated July 28, 2026. https://supplychainattack.org/incident/malicious-code-in-triage-bot-using-sdkv3-npm-16f6s4
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in @omniwatch-wick/cli
Malware discovered in the npm package @omniwatch-wick/cli. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in chain-manager
Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in toll_free (npm)
The npm package toll_free version 1.0.1 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malicious code in blots (npm)
The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.
npmCompromised package