beaver-ui-pagination
visual components
This report shows the evidence for beaver-ui-pagination@35.3.7. 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 payload execution chain unrelated to a pagination component. Lack of lifecycle hooks does not mitigate the reachable runtime execution.
Decision evidence
public snapshot- index.js imports _init.js on every package import.
- _init.js downloads platform-specific binary payloads over HTTPS.
- _init.js falls back to DNS TXT payload retrieval.
- _init.js writes payloads to /var/tmp or temp and executes them detached.
- lib/telemetry.js contains a second configurable downloader/executor chain.
- package.json defines no lifecycle scripts.
- The declared UI entrypoint itself is otherwise minimal.
Source & flagged code
4 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 beaver-ui-pagination@35.3.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing beaver-ui-pagination@35.3.7. 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.