registry / Remote code execution / bnpl-blocks-feature-partners
bnpl-blocks-feature-partners
Bnpl blocks feature partners runtime support module
This report shows the evidence for bnpl-blocks-feature-partners@35.9.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 concrete import-time remote code execution, not legitimate telemetry: the downloaded bytes are executed without validation and are concealed behind a benign wrapper.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of index.js.
Impact
Untrusted remote code executes as the importing application's user.
Mechanism
remote payload download, drop, chmod, and detached execution
Attack narrative
The public entrypoint silently loads _ext.js. On import, it obtains a platform-specific binary over HTTPS from obfuscated Workers hosts or reconstructs one from DNS TXT records, writes it to a temporary location, makes it executable on non-Windows systems, and runs it detached. The payload is neither authenticated nor package-aligned.
AI rationale
This is concrete import-time remote code execution, not legitimate telemetry: the downloaded bytes are executed without validation and are concealed behind a benign wrapper.
Evidence
package.jsonindex.js_ext.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packagesdk.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 _ext.js on every package import.
- _ext.js fetches platform binaries from hidden Workers hosts.
- _ext.js falls back to DNS TXT payload retrieval from wel1.ru hosts.
- _ext.js writes the payload to a temp file, chmods it, and launches it detached via shell/cmd.
- No integrity/signature verification precedes execution.
Evidence against
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent configuration writes were found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_ext.jsView file
3const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L42: const STAMP_TTL = 20362;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
L53: const isWin = _p("platform") === "win32";
L54: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L55: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: if (e || !rr || !rr.length) return r("");
Critical
3Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L3: const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L42: const STAMP_TTL = 20362;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
L53: const isWin = _p("platform") === "win32";
L54: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L55: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: 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.
_ext.jsView on unpkg · L3Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bnpl-blocks-feature-partners@35.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-feature-partners@35.9.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.