registry / Remote code execution / bnpl-blocks-atom-bnpl-notification
bnpl-blocks-atom-bnpl-notification
Lightweight bnpl blocks atom bnpl notification wrapper
This report shows the evidence for bnpl-blocks-atom-bnpl-notification@35.3.8, 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 import-time remote binary loader and detached execution are concrete malicious behavior, not ordinary telemetry. No lifecycle hook is needed because the package entrypoint triggers the payload chain.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of index.js.
Impact
Unconsented remote code execution as the importing user's account.
Mechanism
Remote payload download, DNS fallback, temporary binary drop, and detached execution.
Attack narrative
index.js suppresses errors while importing _runtime.js. That module executes setup immediately, retrieves a platform payload from obfuscated HTTPS mirrors or DNS TXT records, writes it to a temporary executable path, marks it executable on Unix, and starts it detached through /bin/sh or cmd.exe. This provides the package author remote code execution whenever the package is imported.
AI rationale
The import-time remote binary loader and detached execution are concrete malicious behavior, not ordinary telemetry. No lifecycle hook is needed because the package entrypoint triggers the payload chain.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random-hex>
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.dl.wel1.ruext.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 _runtime.js on every package import.
- _runtime.js downloads platform-specific payloads from obfuscated workers.dev mirrors.
- It falls back to DNS TXT payload retrieval from dl.wel1.ru domains.
- Downloaded bytes are written to a temporary executable and launched detached via shell/cmd.
- The behavior is import-time, silent, and unrelated to the exported wrapper API.
Evidence against
- package.json contains no npm lifecycle scripts.
- The public index API itself is a minimal notification wrapper.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_runtime.jsView file
2L3: const https = require("https");
L4: const fs = require("fs");
...
L42: const EXPIRE_SEC = 20215;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
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");
...
L87: try {
L88: require("dns").resolveTxt(d, (e, rr) => {
L89: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L2:
L3: const https = require("https");
L4: const fs = require("fs");
...
L42: const EXPIRE_SEC = 20215;
L43: const _l = (...a) => process.stderr.write("");
L44:
...
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");
...
L87: try {
L88: require("dns").resolveTxt(d, (e, rr) => {
L89: 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.
_runtime.jsView on unpkg · L2Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bnpl-blocks-atom-bnpl-notification@35.3.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-atom-bnpl-notification@35.3.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.