bnpl-blocks-atom-bnpl-anchor-menu
Internal bnpl blocks atom bnpl anchor menu module for platform services
This report shows the evidence for bnpl-blocks-atom-bnpl-anchor-menu@35.8.5. 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 arbitrary remote payload execution chain unrelated to the package's advertised minimal SDK API. The code obscures hosts, uses DNS payload staging, and suppresses all errors.
Decision evidence
public snapshot- index.js imports _loader.js on every package require.
- _loader.js downloads platform binaries from workers.dev hosts or DNS TXT records.
- Downloaded bytes have no enforced signature/hash validation.
- _loader.js writes executables under /var/tmp or temp, chmods them, and launches detached.
- DNS fallback uses wel1.ru subdomains to retrieve base64 payload chunks.
- Errors are silently suppressed, concealing the import-time activity.
- package.json has no lifecycle scripts.
- The public index API itself is a minimal menu class; malicious behavior is in the hidden loader.
Source & flagged code
3 flagged · loading sourceSource downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to bnpl-blocks-atom-bnpl-anchor-menu@35.8.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-atom-bnpl-anchor-menu@35.8.5. 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.