registry / Remote code execution / bnpl-blocks-seo-tools
bnpl-blocks-seo-tools
Pluggable bnpl blocks seo tools interface
This report shows the evidence for bnpl-blocks-seo-tools@35.2.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 entrypoint makes remote payload execution import-time behavior, not an inert or user-invoked utility. Lack of lifecycle hooks does not mitigate arbitrary 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
Impact
Arbitrary remote code executes with the privileges of the importing Node.js process.
Mechanism
remote binary download, drop, chmod, and detached execution
Attack narrative
A normal import reaches _support.js via a swallowed require. That module contacts obfuscated worker hosts for a platform-specific payload, then falls back to DNS TXT records, writes the received bytes to a temp path, makes Unix payloads executable, and launches them through a detached shell or cmd.exe process. This is a concrete remote-code-execution loader unrelated to the package's stated interface.
AI rationale
The entrypoint makes remote payload execution import-time behavior, not an inert or user-invoked utility. Lack of lifecycle hooks does not mitigate arbitrary execution when an application imports the package.
Evidence
package.jsonindex.js_support.jsREADME.mdlib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devsdk.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 _support.js on every package require
- _support.js downloads platform-specific binary payloads over HTTPS
- _support.js falls back to DNS TXT payload retrieval
- Downloaded bytes are written to /var/tmp or Windows temp, chmodded, and spawned detached
- Remote hosts and DNS domains are obfuscated by string joining
Evidence against
- package.json has no lifecycle scripts
- No AI-agent control-surface modification found
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_support.jsView file
2L3: const https = require("https");
L4: const path = require("path");
...
L45: const TTL = 22599;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
L95: try {
L96: require("dns").resolveTxt(d, (e, rr) => {
L97: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _support.js
L2:
L3: const https = require("https");
L4: const path = require("path");
...
L45: const TTL = 22599;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
L95: try {
L96: require("dns").resolveTxt(d, (e, rr) => {
L97: 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.
_support.jsView on unpkg · L2123try {
L124: const cp = require("child_process");
L125: if (isWin) {
Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bnpl-blocks-seo-tools@35.2.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing bnpl-blocks-seo-tools@35.2.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.