bnpl-blocks-desktop-bnpl-floating-button
Shared bnpl blocks desktop bnpl floating button library for backend integration
This report shows the evidence for bnpl-blocks-desktop-bnpl-floating-button@35.7.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-aiThis is a concealed import-time remote binary downloader and executor, unrelated to the declared floating-button library purpose. The absence of an npm lifecycle hook does not mitigate the reachable runtime RCE.
Decision evidence
public snapshot- index.js unconditionally requires _helpers.js on import.
- _helpers.js fetches executable-sized data from shuffled worker hosts.
- It falls back to DNS TXT payload retrieval from *.dl.wel1.ru.
- It writes the payload to a temp path, chmods it, then detached-spawns it via shell/cmd.
- package.json has no lifecycle scripts or dependencies.
- The exported index class is a minimal inert-looking facade; execution is hidden in its import side effect.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_helpers.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to bnpl-blocks-desktop-bnpl-floating-button@35.7.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-desktop-bnpl-floating-button@35.7.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.