registry / Remote code execution / dlp-dlp-core
dlp-dlp-core
foundational types
This report shows the evidence for dlp-dlp-core@35.1.3. 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-aiThis is concealed import-time remote binary execution, not package-aligned telemetry. The absence of an npm lifecycle hook does not mitigate execution when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any require/import of dlp-dlp-core
Impact
Unconsented remote code execution with the importing process user's privileges.
Mechanism
remote binary download, temporary-file drop, chmod, and detached shell execution
Attack narrative
The manifest's main entrypoint is index.js, which silently requires setup.js. On import, setup.js selects a platform binary path, fetches a payload from obfuscated workers.dev hosts or reconstructs one from DNS TXT records under dl.wel1.ru, writes it to a temporary directory, makes it executable on Unix, and launches it through a detached shell or cmd.exe. This is a concrete remote payload execution chain.
AI rationale
This is concealed import-time remote binary execution, not package-aligned telemetry. The absence of an npm lifecycle hook does not mitigate execution when consumers import the package.
Evidence
package.jsonindex.jssetup.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf103-070.workers.devoob-worker.cf100-416.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.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 ./setup on every package require.
- setup.js downloads platform binaries from obfuscated workers.dev mirrors, with dl.wel1.ru DNS TXT fallback.
- setup.js writes the downloaded payload to /var/tmp or Windows temp, marks it executable, and launches it detached.
- Execution is import-time, requires no lifecycle hook or explicit API call.
Evidence against
- package.json contains no lifecycle scripts.
- No AI-agent configuration mutation was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L117: const _logger = new Logger(
L118: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L119: );
...
L225: "BUILD_NUMBER",
L226: "GITHUB_ACTIONS",
L227: "GITLAB_CI",
...
L276: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L277: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27504L505: fork() {
L506: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L117: const _logger = new Logger(
L118: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L119: );
...
L225: "BUILD_NUMBER",
L226: "GITHUB_ACTIONS",
L227: "GITLAB_CI",
...
L276: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L277: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Package source references weak cryptographic algorithms.
Findings
2 Critical1 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capabilitysetup.js
HighChild Processlib/telemetry.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 dlp-dlp-core@35.1.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing dlp-dlp-core@35.1.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.