Which versions of easy-day-js are malicious?

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

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

easy-day-js is a typosquat — you almost certainly intended a legitimately-named package. Remove easy-day-js, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed easy-day-js — how do I know if it already compromised me?

If easy-day-js 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 easy-day-js part of a known attack campaign?

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

Malicious package

easy-day-jsnpm

easy-day-js is a confirmed malicious npm package (MAL-2026-5979) that typosquats a legitimate package to trick installs (malicious version 1.11.22). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in easy-day-js (npm)

MAL-2026-5979

Immediate action

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

npm uninstall easy-day-js

What this malware does

Package name 'easy-day-js' impersonates the popular 'dayjs' library, copying dayjs's author ('iamkun'), homepage (https://day.js.org), repository URL, description, and version number (1.11.22 is a real dayjs release), and bundles dayjs.min.js as main to look legitimate. package.json adds a postinstall hook 'node setup.cjs --no-warnings' that does not exist in real dayjs. setup.cjs is heavily obfuscated with an obfuscator.io-style rotated base64 string array (a0_0x23bf) and decoder (a0_0x1a24) hiding API names ('node:child_process', 'node:fs', 'node:crypto', 'spawn', 'writeFileSync'). At install time it sets NODE_TLS_REJECT_UNAUTHORIZED='0' to disable TLS verification, writes the install directory path to os.tmpdir()/.pkg_history and an encoded buffer to os.tmpdir()/.pkg_logs (staging metadata for the second stage), fetches a JavaScript payload from https://23.254.164.92:8000/update/49890878, writes it to a random hex-named file in os.tmpdir(), spawns it detached with the installer's node interpreter (process.execPath, stdio:'ignore', unref()), and then unlinks setup.cjs to cover its tracks. Classic install-time remote-code-execution dropper combined with brand impersonation of dayjs.

Malicious versions

1 flagged

1.11.22

Indicators of compromise (SHA-256)

8602a5a154b50bb6351900a08fa45d7814c0f152e4379dcae53ccfa0b83db891

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for easy-day-js (version 1.11.22). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easy-day-js across your stack and pipelines.
If you installed it — respond
easy-day-js is a typosquat — you almost certainly intended a legitimately-named package. Remove easy-day-js, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If easy-day-js 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 easy-day-js 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. easy-day-js on npm has been identified as a malicious package (version 1.11.22 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006871

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks easy-day-js-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