Which versions of @ml-toolkit-ts/xgboost are malicious?

The following npm versions of @ml-toolkit-ts/xgboost are flagged malicious: 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate @ml-toolkit-ts/xgboost if I installed it?

@ml-toolkit-ts/xgboost 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 @ml-toolkit-ts/xgboost — how do I know if it already compromised me?

If @ml-toolkit-ts/xgboost was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @ml-toolkit-ts/xgboost across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ml-toolkit-ts/xgboost (2 malicious versions).

Malicious package

@ml-toolkit-ts/xgboostnpm

Advisory published May 12, 2026Updated May 12, 2026

@ml-toolkit-ts/xgboost is a confirmed malicious npm package (MAL-2026-3602) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.3, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ml-toolkit-ts/xgboost (npm)

MAL-2026-3602

Immediate action

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

npm uninstall @ml-toolkit-ts/xgboost

What this malware does

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

2 flagged

1.0.31.0.4

Indicators of compromise (SHA-256)

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @ml-toolkit-ts/xgboost (2 malicious versions).
If you installed it — respond
@ml-toolkit-ts/xgboost 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 @ml-toolkit-ts/xgboost was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @ml-toolkit-ts/xgboost on npm has been identified as a malicious package (versions 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Detect & block this

O3 blocks @ml-toolkit-ts/xgboost-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