bigops-storio-ngrx-component-store
state container
This report shows the evidence for bigops-storio-ngrx-component-store@35.3.4. 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-aiThe malicious chain is directly reachable from the main entrypoint and needs no install hook or explicit user command. The package’s stated state-container purpose does not justify arbitrary remote native payload execution.
Decision evidence
public snapshot- index.js imports _helpers.js on every package import.
- _helpers.js downloads a binary, writes it to /var/tmp, chmods it, and launches it detached.
- Downloaded payloads may come from Workers hosts or DNS TXT records.
- Payload execution is hidden by empty logging and broad error suppression.
- package.json has no lifecycle scripts.
- The exported Store implementation is a simple in-memory state container.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L3A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_helpers.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to bigops-storio-ngrx-component-store@35.3.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-storio-ngrx-component-store@35.3.4. 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.