time-webkit-tag
Time webkit tag provider for microservice architecture
This report shows the evidence for time-webkit-tag@20.1.6. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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-aiThis is a concrete import-time remote-code-execution payload loader, not telemetry behavior. The lack of npm lifecycle hooks does not reduce the runtime compromise risk.
Decision evidence
public snapshot- index.js imports _init.js on every package import.
- _init.js downloads platform binaries from obfuscated workers.dev hosts.
- _init.js falls back to DNS TXT payload retrieval from well1.site domains.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, and detached-spawned.
- No manifest lifecycle hook is needed: import-time start() triggers the chain.
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent configuration mutation 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 · L2Findings
Affected versions and remediation
This report applies to time-webkit-tag@20.1.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing time-webkit-tag@20.1.6. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.