registry / Remote code execution / bnpl-blocks-atom-bnpl-feedback
bnpl-blocks-atom-bnpl-feedback
data mapper
This report shows the evidence for bnpl-blocks-atom-bnpl-feedback@35.7.5. 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-aiDirect source inspection confirms an unconsented import-time remote binary execution chain. The lack of npm lifecycle hooks does not mitigate the reachable entrypoint behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime require/import of the package entrypoint.
Impact
Arbitrary attacker-controlled native code can execute as the importing user's account.
Mechanism
import-time remote payload download, drop, chmod, and detached execution
Attack narrative
index.js silently requires _bridge.js. Its import-time init fetches a platform-specific binary from obfuscated worker hosts, or decodes it from attacker-controlled DNS TXT records. It drops the result to a temporary path, sets executable permissions on non-Windows systems, and starts it through a detached shell or cmd.exe process.
AI rationale
Direct source inspection confirms an unconsented import-time remote binary execution chain. The lack of npm lifecycle hooks does not mitigate the reachable entrypoint behavior.
Evidence
package.jsonindex.js_bridge.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_*Windows Temp/dotnet_diag_*.exe
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf103-070.workers.devoob-worker.cf100-416.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 _bridge.js on every package import.
- _bridge.js downloads platform-specific content over HTTPS.
- _bridge.js reconstructs payloads from DNS TXT records.
- Downloaded content is written to /var/tmp or Windows Temp, made executable, and spawned detached.
- Payload hosts are obfuscated via string concatenation; no user action or consent is required.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by index.js; the independently reachable _bridge.js establishes the attack.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L120: const _logger = new Logger(
L121: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L122: );
...
L228: "BUILD_NUMBER",
L229: "GITHUB_ACTIONS",
L230: "GITLAB_CI",
...
L279: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L280: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27494L495: fork() {
L496: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = dolyame-boxy-atom-bnpl-popup@35.9.3
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.9.3
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsView on unpkg27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L120: const _logger = new Logger(
L121: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L122: );
...
L228: "BUILD_NUMBER",
L229: "GITHUB_ACTIONS",
L230: "GITLAB_CI",
...
L279: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L280: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Package source references weak cryptographic algorithms.
lib/telemetry.jsView on unpkg · L27_bridge.jsView file
4Trigger-reachable chain: manifest.main -> index.js -> _bridge.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const os = require("os");
...
L46: const MAX_AGE = 21557;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: 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.
_bridge.jsView on unpkg · L4Findings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_bridge.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to bnpl-blocks-atom-bnpl-feedback@35.7.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-atom-bnpl-feedback@35.7.5. 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.