Which versions of @umschool/platform are malicious?

The following npm versions of @umschool/platform are flagged malicious: 999.0.0, 999.0.1, 999.0.2. Treat any of these as compromised.

How do I remediate @umschool/platform if I installed it?

@umschool/platform 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.

I already installed @umschool/platform — how do I know if it already compromised me?

If @umschool/platform 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.

Is @umschool/platform part of a known attack campaign?

Yes — @umschool/platform is associated with the IN-MAL-2026-019857, IN-MAL-2026-019855, IN-MAL-2026-019856 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @umschool/platform across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @umschool/platform (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @umschool/platform across your stack and pipelines.

Malicious package

@umschool/platformnpm

@umschool/platform is a confirmed malicious npm package (MAL-2026-16082) 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/platform (npm)

MAL-2026-16082

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @umschool/platform

What this malware does

@umschool/[email protected] is published to public npm under an internal-looking scope with an implausibly high version number, a resolution shape used to override internal builds. Its postinstall.js runs on npm install and performs a bulk harvest of installer-owned secrets: it reads the Kubernetes service-account token and namespace from /var/run/secrets/kubernetes.io/serviceaccount/, /etc/hosts and /etc/resolv.conf, queries cloud instance metadata services (AWS IMDS at 169.254.169.254 including IAM role credentials, ECS task-role credentials via 169.254.170.2 / AWS_CONTAINER_CREDENTIALS_RELATIVE_URI, Azure IMDS, and Yandex/GCP-compatible metadata), calls https://kubernetes.default.svc/api/v1/secrets with the harvested SA token as Bearer authorization, walks up to 8 parent directories reading.env files, and filters process.env against a credential regex (token|secret|key|pass|cred|auth|aws|jwt|api|stripe|sendgrid|twilio|...). The collected data is base64-encoded and POSTed to the hardcoded external endpoint https://akko.requestcatcher.com/dep-confusion-v2. The package's self-label as a 'Dependency Confusion PoC' does not change the effect: any build or CI environment that resolves this public package leaks its cloud IAM credentials, Kubernetes secrets, and environment secrets to an external host.

Malicious versions

3 flagged

999.0.0999.0.1999.0.2

Indicators of compromise (SHA-256)

0fefea4d6708fdfc40e784e5906d588dcf2e0cd98cb809de55f22aaf44b31ce9

bcf64895a777467cc94763bfb942be3c04040ca151fc22753ca48ac4aaecd69c

bf32ebb56edccccf87cabc4f5b811872f541fe79659252092d9d19e431152ec2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @umschool/platform (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @umschool/platform across your stack and pipelines.
If you installed it — respond
@umschool/platform 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/platform 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/platform 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

No. @umschool/platform on npm has been identified as a malicious package (versions 999.0.0, 999.0.1, 999.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019857IN-MAL-2026-019855IN-MAL-2026-019856

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @umschool/platform-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database