registry / Remote code execution / bnpl-blocks-desktop-bnpl-link-group
bnpl-blocks-desktop-bnpl-link-group
Bnpl blocks desktop bnpl link group abstraction layer
This report shows the evidence for bnpl-blocks-desktop-bnpl-link-group@35.4.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 remote payload execution chain, unrelated to the package's advertised abstraction API. No install hook is required for compromise once a consumer imports it.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime import/require of index.js.
Impact
Arbitrary remote code executes with the importing process user's privileges.
Mechanism
import-time staged payload download, drop, and detached execution
Attack narrative
When an application imports this package, index.js silently requires _vendor.js. That module selects a platform-specific endpoint, downloads an opaque binary from rotating Worker hosts or reconstructs it from DNS TXT records, writes it under a misleading randomized temporary filename, makes it executable on Unix, and starts it detached through a shell. A temporary stamp suppresses repeated activity, while telemetry opt-out variables disguise the loader as analytics.
AI rationale
This is a concrete import-time remote payload execution chain, unrelated to the package's advertised abstraction API. No install hook is required for compromise once a consumer imports it.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/package
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _vendor.js on every package import.
- _vendor.js downloads platform binaries from worker hosts or DNS TXT records.
- _vendor.js writes a randomized executable to /var/tmp or Windows Temp.
- _vendor.js chmods then launches the downloaded file detached via shell/cmd.
- Import-time setup uses a hidden temp stamp to limit repeat execution.
Evidence against
- package.json has no lifecycle scripts.
- The exported index API is minimal, but its import triggers the hidden vendor loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_vendor.jsView file
4const crypto = require("crypto");
L5: const https = require("https");
L6: const os = require("os");
...
L42: const STAMP_TTL = 21302;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: 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.
_vendor.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const os = require("os");
...
L42: const STAMP_TTL = 21302;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: 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.
_vendor.jsView on unpkg · L4Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bnpl-blocks-desktop-bnpl-link-group@35.4.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-desktop-bnpl-link-group@35.4.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.