# MAL-2026-11106: Malicious code in date-sanitize-helper (npm)


- **Type:** Malicious package
- **Package:** `date-sanitize-helper` (npm)
- **Published:** 28 Jul 2026

## What is MAL-2026-11106?

MAL-2026-11106 is a malicious package in date-sanitize-helper, published on 28 Jul 2026. 

### Official description

The package is advertised as a date parsing/sanitization helper but its postinstall.js runs automatically on npm install and performs installer-side data collection unrelated to the stated purpose. The script shells out via child_process/exec and curl to gather hostname, current user, id output, sudo -l output, uname, cwd, container indicators, GitHub Actions environment, running process list, and network information. It filters environment variables against a credential keyword set (KEY, TOKEN, SECRET, CREDENTIAL, KUBE, JENKINS, NPM, GEM, CARGO, AZURE, GCP, AWS_, GH_TOKEN, GITHUB_TOKEN) and probes cloud instance-metadata endpoints (AWS 169.254.169.254, Tencent, Aliyun). The aggregated output is base64-encoded and posted via curl to the hardcoded host pzs5w7ntzhsnepwk564lyfdci3oucl0a.oastify.com (a Burp Collaborator subdomain). Postinstall.js contains Chinese-language comments describing a 'compact exfil version', and index.js is an unrelated small color utility, indicating deliberate cover-story metadata.

The OpenSSF Package Analysis project identified 'date-sanitize-helper' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

## What should I do about MAL-2026-11106?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11106 is a malicious package: date-sanitize-helper (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-11106/ (Markdown: https://insights.sbomify.com/MAL-2026-11106/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11106

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11106/
Summaries are generated and may contain mistakes; the official description above is the record.