MAL-2026-16051 Malicious code in @umschool/analytics (npm)
Malicious package
Published
MAL-2026-16051 is a malicious package: @umschool/analytics (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16051/ (Markdown: https://insights.sbomify.com/MAL-2026-16051/index.md)
- Package
- @umschool/analytics
- Registry
- npm
What is MAL-2026-16051?
MAL-2026-16051 is a malicious package in @umschool/analytics, published on 8 Sep 2026.
Official description
@umschool/[email protected] targets the internal @umschool npm scope with an implausibly high version number to force resolution over any private package of the same name. Its postinstall.js runs on npm install and collects host identity (os.hostname, os.userInfo, process.cwd), reads /etc/hostname, /etc/hosts, /etc/resolv.conf, and /proc/version, filters process.env for credential-shaped keys matching a broad regex (token/secret/key/pass/aws/db/jwt/auth/etc.), and walks parent directories to read.env and config.* files. Each payload is base64-encoded and transmitted via three HTTPS GET beacons to akko.requestcatcher.com, with an additional hex-encoded DNS beacon of hostname+user to the same domain. A README/comment self-labeling the code as a 'HARMLESS PoC' does not change the observed behavior: credential-shaped environment variables, dotenv files, and internal network configuration leave the installer's build host to a third-party request-catcher.
What should I do about MAL-2026-16051?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.