LWA-2026-5331 confirmed malware

ts-enum-helper@1.0.0

Malicious code in ts-enum-helper (npm)

T1059.004 · Unix ShellT1552.001 · Credentials In FilesT1613 · Container and Resource DiscoveryT1526 · Cloud Service DiscoveryT1087.004 · Cloud Account DiscoveryT1071.001 · Web ProtocolsT1041 · Exfiltration Over C2 ChannelT1195.002 · Compromise Software Supply Chain

Analysis

Postinstall hook runs a shell script that harvests GCP OAuth tokens from the instance metadata server (metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token) and exfiltrates them to aaronstack[.]com/jules-collect. It then uses the stolen token to probe the Kubernetes API server (kubernetes.default.svc) — listing clusterrolebindings, nodes, secrets (in kube-system, apps, default, kube-public, kube-node-lease, and malysis namespaces), configmaps, deployments, daemonsets, statefulsets, persistentvolumes, jobs, and ingresses — and runs SelfSubjectAccessReviews to map the token's RBAC permissions. It also enumerates ~25 hardcoded GCS buckets (including "npm-analysis", "sd-malysis", "malysis-packages", "rare-signer-437603-p9-*"). All reconnaissance results are exfiltrated to the same endpoint (aaronstack[.]com/jules-collect) with distinct x-source headers (malysis-sysauth-token, malysis-sysauth-results, malysis-sysauth). The script gates on the MALYSIS_ANALYSIS_ID environment variable. The rest of the package is a 21-byte stub (module.exports = {};).

analyzed by
Leitwacht
first seen
Jun 15, 2026, 07:38 AM
analyzed
Jun 15, 2026, 07:39 AM

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.