bnpl-blocks-atom-bnpl-skeleton
Bnpl blocks atom bnpl skeleton SDK for internal consumers
This report shows the evidence for bnpl-blocks-atom-bnpl-skeleton@35.6.3, 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 concrete import-time remote-code-execution chain, not ordinary telemetry. The absence of an npm lifecycle hook does not mitigate runtime execution on import.
Decision evidence
public snapshot- index.js imports _init.js on every package import.
- _init.js downloads platform payloads from three worker hosts.
- _init.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to a temp file, chmodded on Unix, then detached-spawned via shell/cmd.
- No integrity or signature verification is performed before execution.
- package.json contains no lifecycle scripts.
- The documented public API is otherwise a minimal skeleton.
Source & flagged code
5 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_init.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to bnpl-blocks-atom-bnpl-skeleton@35.6.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-atom-bnpl-skeleton@35.6.3. 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.