registry / Remote code execution / bnpl-blocks-component-story-name
bnpl-blocks-component-story-name
Bnpl blocks component story name provider for microservice architecture
This report shows the evidence for bnpl-blocks-component-story-name@35.2.7, 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 advertised SDK. The absence of install hooks does not mitigate execution when an application imports the package.
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, unless opt-out environment variables are set.
Impact
Unconsented arbitrary native code execution under the importing process user.
Mechanism
Import-time remote binary download and detached execution.
Attack narrative
The public entrypoint silently loads _polyfill.js. Its start() function runs immediately, retrieves a binary from obfuscated worker hosts or DNS TXT records, saves it under a temporary cache-like filename, makes it executable on Unix, then launches it detached through a shell or cmd.exe.
AI rationale
This is a concrete import-time remote payload execution chain unrelated to the advertised SDK. The absence of install hooks does not mitigate execution when an application imports the package.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.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 _polyfill.js on every package import.
- _polyfill.js downloads OS-specific binary payloads.
- Downloaded bytes are written, chmodded, and spawned detached.
- Payload hosts are obfuscated and include DNS TXT fallback.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
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");
...
L121: const _logger = new Logger(
L122: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L123: );
...
L230: "BUILD_NUMBER",
L231: "GITHUB_ACTIONS",
L232: "GITLAB_CI",
...
L281: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L282: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27500L501: fork() {
L502: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L121: const _logger = new Logger(
L122: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L123: );
...
L230: "BUILD_NUMBER",
L231: "GITHUB_ACTIONS",
L232: "GITLAB_CI",
...
L281: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L282: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Findings
2 Critical2 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similarity_polyfill.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptolib/telemetry.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bnpl-blocks-component-story-name@35.2.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-component-story-name@35.2.7. 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.