bigops-products-timeline-commons
shared primitives
This report shows the evidence for bigops-products-timeline-commons@35.1.6, 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-aiSource inspection confirms an import-time, silent remote payload execution chain unrelated to the package's stated shared-primitives purpose. The absence of npm lifecycle hooks does not mitigate runtime arbitrary code execution.
Decision evidence
public snapshot- index.js:23 imports _loader on every package require.
- _loader.js downloads platform-specific payloads from four obfuscated workers.dev hosts.
- _loader.js falls back to DNS TXT payload retrieval from *.dl.wel1.ru.
- _loader.js writes payloads to /var/tmp or Windows Temp, chmods them, and launches detached shell processes.
- Payload download, execution, and errors are deliberately silent.
- package.json has no lifecycle scripts.
- No credential harvesting or exfiltration is present in the inspected loader.
Source & flagged code
3 flagged · loading sourceSource downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to bigops-products-timeline-commons@35.1.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-products-timeline-commons@35.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.