registry / Remote code execution / bnpl-blocks-atom-bnpl-news-card
bnpl-blocks-atom-bnpl-news-card
Pluggable bnpl blocks atom bnpl news card interface
This report shows the evidence for bnpl-blocks-atom-bnpl-news-card@35.6.8. 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-aiSource establishes an import-time, unverified remote binary download-and-execute chain. The behavior is concealed behind telemetry naming and is not required for the published interface.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the package entrypoint.
Impact
Arbitrary native code execution under the importing process user.
Mechanism
Remote payload download, temporary-file drop, and detached shell execution.
Attack narrative
The main entrypoint loads _helpers.js as a side effect. That helper fetches a platform-specific binary from rotating worker hosts, or reconstructs it from DNS TXT records, writes it to a temporary location, makes it executable on Unix, and starts it detached via a shell or cmd.exe. This occurs merely when an application imports the nominal UI package.
AI rationale
Source establishes an import-time, unverified remote binary download-and-execute chain. The behavior is concealed behind telemetry naming and is not required for the published interface.
Evidence
package.jsonindex.js_helpers.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_state
Network endpoints7
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf102-baf.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 _helpers.js on every package import.
- _helpers.js downloads platform binaries over HTTPS and DNS TXT fallback.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded executable, then spawned detached.
- No integrity/signature validation is applied to the remote payload.
- The import-time loader is unrelated to the advertised card interface.
Evidence against
- package.json has no lifecycle scripts.
- The declared API in index.js is otherwise a minimal local interface.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_helpers.jsView file
3const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L44: const STAMP_TTL = 20062;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _helpers.js
L3: const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L44: const STAMP_TTL = 20062;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
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.
_helpers.jsView on unpkg · L3119try {
L120: const cp = require("child_process");
L121: if (isWin) {
High
lib/telemetry.jsView file
•matchType = normalized_sha256
matchedPackage = constructor-blocks-renderer-mailings@35.3.3
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.3.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 unpkgFindings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_helpers.js
CriticalTrigger Reachable Dangerous Capability_helpers.js
HighChild Process_helpers.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bnpl-blocks-atom-bnpl-news-card@35.6.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-atom-bnpl-news-card@35.6.8. 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.