digital-interview-digital-interview-corenpm
digital-interview-digital-interview-core is a confirmed malicious npm package (MAL-2026-12362) that executes malicious code on install (malicious version 20.5.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in digital-interview-digital-interview-core (npm)
What this malware does
On require() of the package, helpers.js downloads a platform-specific binary from Cloudflare workers.dev hosts whose names are reconstructed at runtime via array-join string splits (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT chunked fallback across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (.cache<rand>,.analytics_state, or dotnet_diag_<rand>.exe to masquerade as.NET telemetry), chmod 0755 is applied, and the file is spawned detached via /bin/sh -c or cmd. No hash or signature verification is performed on the downloaded content, and the destinations are not the package's publisher. The behavior is gated by a run-once freshness marker and DISABLE_TELEMETRY env-var checks used as cover, and hosts and file names are string-split-obfuscated to evade static analysis. This yields arbitrary remote code execution on the installer's host at load time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for digital-interview-digital-interview-core (version 20.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging digital-interview-digital-interview-core across your stack and pipelines.
If you installed it — respond
Remove digital-interview-digital-interview-core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If digital-interview-digital-interview-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks digital-interview-digital-interview-core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks digital-interview-digital-interview-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.