Which versions of date-sanitize-helper are malicious?

The following npm versions of date-sanitize-helper are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate date-sanitize-helper if I installed it?

date-sanitize-helper 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 date-sanitize-helper — how do I know if it already compromised me?

If date-sanitize-helper 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 date-sanitize-helper part of a known attack campaign?

Yes — date-sanitize-helper is associated with the IN-MAL-2026-010880 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 date-sanitize-helper 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 date-sanitize-helper (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging date-sanitize-helper across your stack and pipelines.

Malicious package

date-sanitize-helpernpm

date-sanitize-helper is a confirmed malicious npm package (MAL-2026-11106) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in date-sanitize-helper (npm)

MAL-2026-11106

Immediate action

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

npm uninstall date-sanitize-helper

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0ad5bc011fffec78eedbae93d69fa652c21868e6a8492f3c4a34cdb08dffd6e1

33b6764b7711cfa03cf6b3a2f70e24b3256a61ac9319d45200ada236fe7c3ed2

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 date-sanitize-helper (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging date-sanitize-helper across your stack and pipelines.
If you installed it — respond
date-sanitize-helper 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 date-sanitize-helper 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 date-sanitize-helper 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. date-sanitize-helper on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010880

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks date-sanitize-helper-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