registry / Remote code execution / bnpl-blocks-mobile-bnpl-floating-button
bnpl-blocks-mobile-bnpl-floating-button
mobile SDK
This report shows the evidence for bnpl-blocks-mobile-bnpl-floating-button@35.3.6. 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-aiThe import-time remote payload execution chain is explicit in source and requires no user setup action. The unused-looking telemetry module does not mitigate this behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Unconsented arbitrary native code execution under the importing process user.
Mechanism
remote binary download, drop, and detached execution
Attack narrative
A normal import reaches _support.js, which rate-limits itself with a temp marker, retrieves a platform-specific binary from obfuscated Workers hosts or DNS TXT records, writes it to a temp path, makes Unix payloads executable, and starts them detached via /bin/sh or cmd.exe. This is a concrete remote code-execution chain, not package-aligned SDK behavior.
AI rationale
The import-time remote payload execution chain is explicit in source and requires no user setup action. The unused-looking telemetry module does not mitigate this behavior.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagedns TXT: c.sdk.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 _support.js on every package import.
- _support.js downloads opaque binaries over HTTPS or DNS TXT.
- _support.js writes payloads to temporary storage, chmods them, then launches detached shells.
- Remote hosts are obfuscated by string concatenation and execution errors are suppressed.
Evidence against
- package.json has no lifecycle scripts.
- Public index API is otherwise a minimal SDK stub.
- No credential or environment harvesting was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L47: const STAMP_TTL = 20430;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L97: try {
L98: require("dns").resolveTxt(d, (e, rr) => {
L99: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _support.js
L4: const os = require("os");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L47: const STAMP_TTL = 20430;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L97: try {
L98: require("dns").resolveTxt(d, (e, rr) => {
L99: 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.
_support.jsView on unpkg · L4Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bnpl-blocks-mobile-bnpl-floating-button@35.3.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-mobile-bnpl-floating-button@35.3.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.