Which versions of note-utilities are malicious?

The following npm versions of note-utilities are flagged malicious: 2.1.2. Treat any of these as compromised.

How do I remediate note-utilities if I installed it?

Remove note-utilities 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 note-utilities — how do I know if it already compromised me?

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

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

Malicious package

note-utilitiesnpm

Malicious code in note-utilities (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10418

Immediate action

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

npm uninstall note-utilities

What this malware does

The package masquerades as a pino-style logger (keywords fast/logger/stream/json; lib/ contents copied from pinojs/pino) but ships an additional loader at lib/vcall.js. On require, index.js spawns a detached node lib/vcall.js child (detached + unref so it outlives the parent). vcall.js performs an HTTPS GET to https://api.jsonsilo.com/public/94b14d9d-6286-4b13-a7fe-8442e55a31b4, takes the returned data.model string, and passes it to Function.constructor("require", src) before invoking it with the real require. Any JavaScript the third-party JSON hosting endpoint returns runs in the installer's Node process with full module-loading access. The endpoint is attacker-mutable, and the pino-style logger surface is a cover story unrelated to the loader.

Malicious versions

1 flagged

2.1.2

Indicators of compromise (SHA-256)

4f093c8536c89f9d6c524ae212051fc45a5244d910afd8ee3abe30698f15b75d

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

Campaign

IN-MAL-2026-009829

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks note-utilities-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