Which versions of deposits-common are malicious?

The following npm versions of deposits-common are flagged malicious: 35.5.4. Treat any of these as compromised.

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

Remove deposits-common 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.

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

If deposits-common 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-common part of a known attack campaign?

Yes — deposits-common is associated with the IN-MAL-2026-015108 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-common 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-common (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deposits-common across your stack and pipelines.

Malicious package

deposits-commonnpm

deposits-common is a confirmed malicious npm package (MAL-2026-12690) that executes malicious code on install (malicious version 35.5.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in deposits-common (npm)

MAL-2026-12690

Immediate action

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

npm uninstall deposits-common

What this malware does

index.js requires./support on module load. support.js reconstructs obfuscated hostnames via string split-and-join (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev) and, if HTTPS retrieval fails, falls back to a DNS-TXT covert channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, iteratively resolving numbered TXT records and base64-concatenating the chunks. The resulting bytes are written to /var/tmp or %TEMP% under a disguised name (dotnet_diag<rand>.exe on Windows,.cache<rand> on POSIX), chmod 0755, and spawned detached via spawn("/bin/sh") or spawn("cmd"). No hash or signature verification is performed. The loader honors DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK to remain silent in sandboxes and writes a.analytics_state stamp file to gate re-execution. The delivery infrastructure is unrelated to the package's stated purpose of "shared primitives".

Malicious versions

1 flagged

35.5.4

Indicators of compromise (SHA-256)

a6d03bd134745bb66c8ba26a5ee1ddd2f9417eab449bd8ca7a4c649064cf38f1

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for deposits-common (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deposits-common across your stack and pipelines.
If you installed it — respond
Remove deposits-common 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 deposits-common 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-common 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-common on npm has been identified as a malicious package (version 35.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015108

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks deposits-common-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database