Which versions of react-editable-calendar are malicious?

The following npm versions of react-editable-calendar are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate react-editable-calendar if I installed it?

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

I already installed react-editable-calendar — how do I know if it already compromised me?

If react-editable-calendar 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 react-editable-calendar part of a known attack campaign?

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

Malicious package

react-editable-calendarnpm

Malicious code in react-editable-calendar (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6547

Immediate action

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

npm uninstall react-editable-calendar

What this malware does

On npm install, the package's preinstall hook runs node dist/index.d.js. That file base64-decodes a payload which fetches JavaScript from https://everydaynodechecker-39143n.vercel.app/api/key?mem=master and passes the response to eval. The eval identifier is obfuscated by constructing it from character codes [101,118,97,104] and invoking it via globalThis[tag](text) rather than appearing as a literal in source. The result is arbitrary attacker-controlled JavaScript execution on the installer's machine at install time, from an anonymous third-party host. The package name mimics common React calendar component naming and ships empty author metadata, with a minimal dist tree whose only auto-executed code is the remote-eval dropper.

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

9b35fd7baa18320cbcaf6fbb6fbabb6139dd48264cd1f09d0461a8877c1f873f

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 react-editable-calendar (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-editable-calendar across your stack and pipelines.
If you installed it — respond
react-editable-calendar is a typosquat — you almost certainly intended a legitimately-named package. Remove react-editable-calendar, 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 react-editable-calendar 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 react-editable-calendar 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. react-editable-calendar on npm has been identified as a malicious package (version 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007679

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-editable-calendar-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