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
- resolvedcritical
Malicious code in @aligntech-cw/alignerfit (npm)
Malicious code was discovered in the npm package @aligntech-cw/alignerfit. The package was identified by the OpenSSF malicious-packages project and assigned identifier MAL-2024-1743.
npmCompromised package - resolvedcritical
Malicious code in @akunsansan0/susu10 (npm)
@akunsansan0/susu10 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to the npm registry. The package was part of a tea.xyz token reward campaign that flooded npm with similar malicious packages.
npmCompromised package - containedcritical
Malicious code in @antv/f-wx (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 packages, including @antv/f-wx. Each version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials via the GitHub API and establishes persistence through CI/CD workflow injection and system daemons.
Mini Shai HuludTeamPCPnpmOtherAccount takeoverCompromised packageMalicious commit - resolvedcritical
Malicious code in @akunsansan0/susu11 (npm)
@akunsansan0/susu11 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The package modifies package.json, changes version numbers, and continuously pollutes the npm registry with variants.
npmCompromised package