Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

date-format-helper2npm

Malicious code in date-format-helper2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6301
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall date-format-helper2

What this malware does

Package is advertised as a React date-formatting utility, but its postinstall.js performs targeted credential harvesting on npm install. The script reads Coze workload identity environment variables (COZE_WORKLOAD_API_TOKEN, COZE_WORKLOAD_IDENTITY_CLIENT_ID, COZE_WORKLOAD_IDENTITY_CLIENT_SECRET, COZE_WORKLOAD_IDENTITY_TOKEN_ENDPOINT, COZE_PROJECT_SPACE_ID), uses them to mint OAuth access tokens via three grant types (client_credentials, token-exchange, and a JSON body variant) against the configured token endpoint, enumerates ~30 Coze API paths against api.coze.cn / integration.coze.cn / api.coze.com using the minted tokens, and POSTs the env values, the issued tokens, and the API responses over plaintext HTTP to http://2e3bkumw.requestrepo.com — a public request-capture sinkhole controlled by the attacker. The advertised date-helper functionality in index.js is unrelated cover for the install-time credential theft. An installer running npm install in CI or a developer environment with Coze credentials in scope would have their workload identity stolen and the attacker could impersonate that workload against Coze APIs.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

7 flagged
1.0.01.0.21.0.31.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

04a1e5571acbf5901d113811c19983d13f2dc0d532127445c2b16ed650d6b57c
66c1775ce65ad47476ee1a0f1c7c5373e61466ec3eb4543cc658e67d2de22960
78c0b87795b33cc06d2aa096cca532f61aa0f600ec888be07b7bcfc2ea1c6cad
ac54599f5ebf64585175c7d4b7bd626097f248c04aca277737e457940bd46373
bd77add56411d8c62f428c859ce630c4604640766bb7eb3b359426d782737d5b
d8b44f47c55950a88fb3842670fa061aa6b9c08cb3f048e0f43bfc4be2789009
f1d638ba3203a606c5e4dd2187aed12eae58a0e3144b6df61d6495182dd27654
a13b8fd2717f710497955f390bdf36a5b52abda37b7f3bd47f737f98bfbbb5b4

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for date-format-helper2 (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging date-format-helper2 across your stack and pipelines.

  2. If you installed it — respond

    date-format-helper2 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.

  3. Did it already run?

    If date-format-helper2 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.

  4. How O3 protects you

    O3 blocks date-format-helper2 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-format-helper2 on npm has been identified as a malicious package (versions 1.0.0, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007227IN-MAL-2026-007229IN-MAL-2026-007230IN-MAL-2026-007231IN-MAL-2026-007228IN-MAL-2026-007233IN-MAL-2026-007232GHSA-j29f-62x7-hj66

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks date-format-helper2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

date-format-helper2 (npm) malicious package — MAL-2026-6301 | O3 Security