registry / Remote code execution / candy-candy-core
candy-candy-core
foundational types
This report shows the evidence for candy-candy-core@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-aiThe package entrypoint contains an import-time, obfuscated downloader/executor with no legitimate API relationship to the declared foundational-types package. This establishes concrete malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of candy-candy-core
Impact
Arbitrary code execution under the consuming application's user account.
Mechanism
import-time remote binary download, drop, chmod, and detached execution
Attack narrative
The main entrypoint suppresses errors while loading _polyfill.js. That module immediately contacts obfuscated worker endpoints or obtains a payload through DNS TXT records, saves a sufficiently large response as a temporary executable, sets execute permissions on Unix, and launches it detached through a shell or cmd.exe. This is an unconsented remote code execution chain triggered simply by importing the package.
AI rationale
The package entrypoint contains an import-time, obfuscated downloader/executor with no legitimate API relationship to the declared foundational-types package. This establishes concrete malicious behavior.
Evidence
index.js_polyfill.jslib/telemetry.jspackage.json
Network endpoints8
oob-worker.cf99-9b3.workers.devoob-worker.cf103-070.workers.devoob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devsdk.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 _polyfill.js during every package require.
- _polyfill.js fetches platform-specific payloads from worker hosts and DNS TXT records.
- _polyfill.js writes the downloaded payload to /var/tmp or Windows temp, makes it executable, then detached-spawns it.
- The payload download and execution occur automatically at import time with no user action.
Evidence against
- package.json contains no lifecycle scripts.
- lib/telemetry.js is not imported by the package entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27492L493: fork() {
L494: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = checkout-molecule-mobile-status-sheet@35.7.9
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.7.9
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.jsFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to candy-candy-core@35.2.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing candy-candy-core@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.