Which versions of deposits-overnight are malicious?

The following npm versions of deposits-overnight are flagged malicious: 20.8.5, 35.5.9. Treat any of these as compromised.

How do I remediate deposits-overnight if I installed it?

deposits-overnight is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed deposits-overnight — how do I know if it already compromised me?

If deposits-overnight 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.

Is deposits-overnight part of a known attack campaign?

Yes — deposits-overnight is associated with the IN-MAL-2026-014743, IN-MAL-2026-015098 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find deposits-overnight across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for deposits-overnight (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deposits-overnight across your stack and pipelines.

Malicious package

deposits-overnightnpm

deposits-overnight is a confirmed malicious npm package (MAL-2026-12361) that steals credentials and exfiltrates sensitive data (malicious versions 20.8.5, 35.5.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in deposits-overnight (npm)

MAL-2026-12361

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall deposits-overnight

What this malware does

On require of the package, index.js loads./init.js, which selects a platform-specific endpoint, downloads a native executable from obfuscated Cloudflare Workers hosts (hostnames assembled via split-and-join, e.g. 'oob-worker.cf99-9b3.wo' + 'rkers.d' + 'ev'), with a DNS TXT chunked-download fallback under *.dl.well1.site. The payload is written to /var/tmp or %TEMP% under disguised filenames such as dotnet_diag.exe or.cache_, chmod'd to 0755 on Unix, and spawned detached via cp.spawn('/bin/sh',['-c',fp+' &'],{detached:true}) (or cmd on Windows). A.analytics_state stamp file throttles re-execution, and DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env vars provide a cover story. lib/telemetry.js bundles equivalent dropper primitives (base64 payload assembly, dynamic fs['chmod'+'Sync'], require('child_'+'process'), spawn('/bin/sh',['-c',filePath+' &'])) as a secondary implementation. The package exposes no functionality that would justify fetching and executing an opaque native binary from anonymous infrastructure at import time.

Malicious versions

2 flagged

20.8.535.5.9

Indicators of compromise (SHA-256)

9065d908318bcb4d0db09498a3c52ab32951d889d03acf4d7c3fee12821271cf

d1f37827f0f32998c4e94d28910916f2d959fa2e0665be7dd3be2a2d9b9c97de

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for deposits-overnight (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deposits-overnight across your stack and pipelines.
If you installed it — respond
deposits-overnight is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If deposits-overnight 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 deposits-overnight 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

No. deposits-overnight on npm has been identified as a malicious package (versions 20.8.5, 35.5.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014743IN-MAL-2026-015098

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks deposits-overnight-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database