bnpl-blocks-atom-bnpl-action-card
Bnpl blocks atom bnpl action card runtime support module
This report shows the evidence for bnpl-blocks-atom-bnpl-action-card@35.4.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 concrete, automatically reachable remote binary execution unrelated to the stated card-interface functionality. No install hook is needed because ordinary import activates it.
Decision evidence
public snapshot- index.js imports _loader.js on every package import.
- _loader.js downloads platform binaries from hard-coded worker hosts or DNS TXT records.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded on Unix, and launched detached.
- No hash or signature is verified despite the integrity-check comment.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the package entrypoint.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to bnpl-blocks-atom-bnpl-action-card@35.4.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-atom-bnpl-action-card@35.4.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.