claims-to-iso-string-with-timezone
Internal claims to iso string with timezone module for platform services
This report shows the evidence for claims-to-iso-string-with-timezone@35.7.2, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package's documented claims-conversion API does not require a covert native downloader or detached payload execution. The executable payload is remote-controlled and runs automatically at import time.
Decision evidence
public snapshot- index.js imports _init.js during normal package import.
- _init.js downloads platform-specific bytes from rotating workers.dev hosts.
- _init.js can retrieve a base64 payload via DNS TXT records.
- _init.js writes the payload to /var/tmp or Windows Temp, marks it executable, and spawns it detached.
- Remote payload hosts and DNS domains are concealed by fragmented strings.
- package.json has no lifecycle scripts.
- No AI-agent configuration or credential-file access was found.
Source & flagged code
3 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_init.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to claims-to-iso-string-with-timezone@35.7.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-to-iso-string-with-timezone@35.7.2. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.