Which versions of @daylightqc/date-fmt-lite are malicious?

The following npm versions of @daylightqc/date-fmt-lite are flagged malicious: 1.0.0, 1.0.1, 1.1.1, 1.1.2. Treat any of these as compromised.

How do I remediate @daylightqc/date-fmt-lite if I installed it?

@daylightqc/date-fmt-lite 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 @daylightqc/date-fmt-lite — how do I know if it already compromised me?

If @daylightqc/date-fmt-lite 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 @daylightqc/date-fmt-lite part of a known attack campaign?

Yes — @daylightqc/date-fmt-lite is associated with the IN-MAL-2026-010866, IN-MAL-2026-011078, IN-MAL-2026-011079 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 @daylightqc/date-fmt-lite 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 @daylightqc/date-fmt-lite (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @daylightqc/date-fmt-lite across your stack and pipelines.

Malicious package

@daylightqc/date-fmt-litenpm

@daylightqc/date-fmt-lite is a confirmed malicious npm package (MAL-2026-11041) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.1.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @daylightqc/date-fmt-lite (npm)

MAL-2026-11041

Immediate action

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

npm uninstall @daylightqc/date-fmt-lite

What this malware does

The package declares a postinstall script (postinstall.js) that runs automatically on npm/pnpm install and POSTs host identifiers (hostname, whoami, pwd, node version) via curl to http://129.204.76.212:9999/rce-poc. On require of index.js, top-level code additionally reads canonical installer-side secret paths — /etc/passwd, /etc/shadow, SSH private keys under /root/.ssh and /home/*/.ssh, ~/.npmrc,.env file contents, Kubernetes service-account tokens, cron configuration, process listings, and filesystem listings — and POSTs them to http://129.204.76.212:9999/report. The same code queries cloud instance-metadata endpoints (AWS 169.254.169.254, GCP metadata, AliCloud 100.100.100.200, Tencent metadata.tencentyun.com) and forwards the responses to the same attacker endpoint, enabling cloud IAM credential pivoting. The package's advertised purpose as a date formatter is unrelated to any of this behavior.

The OpenSSF Package Analysis project identified '@daylightqc/date-fmt-lite' @ 1.1.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

4 flagged

1.0.01.0.11.1.11.1.2

Indicators of compromise (SHA-256)

70c4984ac7bf7b1e15e3b449e924fb4178a1e5667b0aee8b282bb796bbe9623c

daefee06d39dc86287fd24855b4b3e81363b9f3fbe2fb3c6dfbf3ed7d6e739f2

db71d0491101b0206b9559efff4f0ccbe12eb86d703c3e58660d78a6ea07e397

62c563208137dbdd6b4c26764222942e2b81e815349b596518ff4db5a652b2bf

5ccf2110a8d05c2219f19911ee0cc705ae5b8198940055e34627ddc4cbbbd438

642c7a51607511cefad6c1ed05e0fb2e48886760402ade6c7477193a805d3002

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

Campaign

IN-MAL-2026-010866IN-MAL-2026-011078IN-MAL-2026-011079

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @daylightqc/date-fmt-lite-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