registry / Remote code execution / bnpl-blocks-atom-bnpl-store-button
bnpl-blocks-atom-bnpl-store-button
data store bindings
This report shows the evidence for bnpl-blocks-atom-bnpl-store-button@35.2.8, 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 binary execution, unrelated to the declared state-management functionality. Lack of lifecycle hooks does not mitigate runtime compromise on package use.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of the package entrypoint.
Impact
Unconsented arbitrary native code execution under the importing user's privileges.
Mechanism
import-time remote binary download and detached execution
Attack narrative
A normal import reaches index.js, which suppresses errors while requiring _loader.js. The loader fingerprints the OS, fetches a platform-specific executable from rotating worker hosts or reconstructs it from DNS TXT records, writes it to a temporary path, marks it executable on Unix, and starts it detached via a shell or cmd.exe.
AI rationale
This is a concrete import-time staged payload chain with remote binary execution, unrelated to the declared state-management functionality. Lack of lifecycle hooks does not mitigate runtime compromise on package use.
Evidence
package.jsonindex.js_loader.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports ./_loader on every package import.
- _loader.js downloads platform-specific payloads over HTTPS.
- _loader.js falls back to DNS TXT payload retrieval.
- Downloaded bytes are written, chmodded, and launched detached.
- Remote hosts and payload execution are hidden behind telemetry-like names.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent configuration writes found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_loader.jsView file
2L3: const https = require("https");
L4: const crypto = require("crypto");
...
L43: const TTL = 20648;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _loader.js
L2:
L3: const https = require("https");
L4: const crypto = require("crypto");
...
L43: const TTL = 20648;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L2Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_loader.js
CriticalTrigger Reachable Dangerous Capability_loader.js
HighChild Process_loader.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bnpl-blocks-atom-bnpl-store-button@35.2.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-atom-bnpl-store-button@35.2.8. 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.