registry / Remote code execution / bnpl-blocks-mobile-bnpl-card-gallery
bnpl-blocks-mobile-bnpl-card-gallery
device integration
This report shows the evidence for bnpl-blocks-mobile-bnpl-card-gallery@35.4.3, 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-aiThe package’s import path performs an unconsented download-and-execute chain with obfuscated infrastructure and no validation. The absence of npm lifecycle hooks does not mitigate execution on normal runtime import.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of the package main entrypoint.
Impact
Unconsented arbitrary native-code execution under the importing process user.
Mechanism
Remote binary download, drop, chmod, and detached execution.
Attack narrative
Requiring index.js silently requires _vendor.js. Its start routine contacts obfuscated workers.dev mirrors for a platform-specific executable, falls back to chunked DNS TXT retrieval, writes the received bytes into a temp file, marks non-Windows files executable, and starts the file through a detached shell or cmd.exe process. The similarly structured telemetry file contains the same loader capability but is not needed for the reachable attack chain.
AI rationale
The package’s import path performs an unconsented download-and-execute chain with obfuscated infrastructure and no validation. The absence of npm lifecycle hooks does not mitigate execution on normal runtime import.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/package/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 on every package import.
- _vendor.js downloads platform-specific binaries over HTTPS or DNS TXT.
- _vendor.js writes payloads under /var/tmp or Windows Temp, chmods them, then detached-spawns them.
- Remote hosts and DNS fallback domains are obfuscated in source.
- No payload signature or integrity verification is performed.
Evidence against
- package.json has no lifecycle scripts.
- The entrypoint suppresses _vendor errors, but still invokes it at import time.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_vendor.jsView file
2L3: const https = require("https");
L4: const path = require("path");
...
L47: const CACHE_TTL = 21312;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L2:
L3: const https = require("https");
L4: const path = require("path");
...
L47: const CACHE_TTL = 21312;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: 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 · L2Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bnpl-blocks-mobile-bnpl-card-gallery@35.4.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-mobile-bnpl-card-gallery@35.4.3. 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.