Malicious code in @al-ui/useappinsights (npm)
Malicious code was discovered in the npm package @al-ui/useappinsights. The package was identified by the OpenSSF malicious-packages project as containing malicious code.
- Disclosed
- Last updated
- Blast radius
- Potentially all projects that installed affected versions of @al-ui/useappinsights
- Ecosystems
- Attack vectors
- Affected entities
- @al-ui/useappinsights
The npm package @al-ui/useappinsights was found to contain malicious code and was cataloged by the OpenSSF's malicious-packages project (identifier MAL-2025-755). The package was published to the npm registry and could have been installed by developers as a dependency in their projects.\n\nThis incident was identified and reported through the OpenSSF's malicious-packages repository, which tracks known malicious packages across package ecosystems. The advisory was published on GitHub's advisory database (GHSA-9chj-fc74-95g9) on 2026-07-26.\n\nAny project that installed affected versions of @al-ui/useappinsights may have been compromised by the malicious code embedded in the package.
Indicators of compromise
- Packages
- @al-ui/useappinsights
Remediation
- Remove @al-ui/useappinsights from all projects and dependencies
- Audit project dependencies for any suspicious activity or unauthorized changes
- Review npm package.lock or yarn.lock files to identify when the malicious package was installed
- Consider rotating any credentials or secrets that may have been exposed
- Update to a clean version of the package if a legitimate replacement is available, or use an alternative package
Sources
- GitHub Advisory GHSA-9chj-fc74-95g9 · GitHub Advisory Database
Cite this entry
"Malicious code in @al-ui/useappinsights (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2026; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-al-ui-useappinsights-npm-1nh6o1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - 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 - 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 - 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