Which versions of caspian-day-js are malicious?

The following npm versions of caspian-day-js are flagged malicious: 1.11.23. Treat any of these as compromised.

How do I remediate caspian-day-js if I installed it?

Remove caspian-day-js 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is caspian-day-js part of a known attack campaign?

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

Can O3 Security detect caspian-day-js in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking caspian-day-js and packages like it before any post-install script runs.

Malicious package

caspian-day-jsnpm

Malicious code in caspian-day-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5892

Immediate action

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

npm uninstall caspian-day-js

What this malware does

caspian-day-js impersonates the popular dayjs package: package.json copies author iamkun, homepage day.js.org, and repo github.com/iamkun/dayjs.git, and ships an unmodified dayjs.min.js as main so require('caspian-day-js') appears functional. The malicious payload is in the lifecycle hook: package.json declares postinstall: node setup.cjs. setup.cjs is heavily obfuscated (obfuscator.io-style string-array with a custom base64 decoder) and at install time sets NODE_TLS_REJECT_UNAUTHORIZED='0', fetches a remote JavaScript payload, writes it to <tmpdir>/<12-hex>.js, then spawns process.execPath on the dropped file (detached, stdio:'ignore', windowsHide:true) with the C2 endpoint 23.254.164.123:443 passed as argv[1], and finally unlinks setup.cjs to erase traces. Every machine running npm install caspian-day-js executes attacker-controlled JavaScript with TLS verification disabled, contacting 23.254.164.123:443.

Malicious versions

1 flagged

1.11.23

Indicators of compromise (SHA-256)

895fe8e087ec7af36d61e8a6972f484e70bc1b828374ae83cef9ff4a927f7b55

Frequently asked questions

No. caspian-day-js on npm has been identified as a malicious package (version 1.11.23 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006769

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection