@umschool/analyticsnpm
@umschool/analytics is a confirmed malicious npm package (MAL-2026-16051) that steals credentials and exfiltrates sensitive data (malicious versions 999.0.0, 999.0.1, 999.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @umschool/analytics (npm)
What this malware does
@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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @umschool/analytics (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @umschool/analytics across your stack and pipelines.
If you installed it — respond
@umschool/analytics is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @umschool/analytics was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @umschool/analytics before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @umschool/analytics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.