dolyame-boxy-mobile-bnpl-button-set
native bridge
This report shows the evidence for dolyame-boxy-mobile-bnpl-button-set@35.8.1, 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 staged payload chain with remote code execution, not ordinary telemetry. The unused telemetry file also contains materially similar downloader/launcher primitives, reinforcing intentional concealment.
Decision evidence
public snapshot- index.js imports _shim.js on every package import.
- _shim.js runs immediately and fetches platform payloads over HTTPS or DNS TXT.
- Downloaded bytes are written to a temp executable path, chmodded on Unix, and spawned detached.
- Remote hosts are obfuscated by string concatenation and include workers.dev and wel1.ru domains.
- Payload execution is silent; errors are swallowed and a temp stamp suppresses repeats.
- package.json contains no lifecycle scripts.
- The exported button-set class itself is minimal; the malicious behavior is the hidden import-time shim.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_shim.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to dolyame-boxy-mobile-bnpl-button-set@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-mobile-bnpl-button-set@35.8.1. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.