Which versions of @signals-notebook/annotation-editor are malicious?

The following npm versions of @signals-notebook/annotation-editor are flagged malicious: 2.2.60-630109c. Treat any of these as compromised.

How do I remediate @signals-notebook/annotation-editor if I installed it?

Remove @signals-notebook/annotation-editor 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 @signals-notebook/annotation-editor — how do I know if it already compromised me?

If @signals-notebook/annotation-editor 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.

How do I find @signals-notebook/annotation-editor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @signals-notebook/annotation-editor (version 2.2.60-630109c).

Malicious package

@signals-notebook/annotation-editornpm

Advisory published Nov 2, 2026Updated Nov 4, 2026

@signals-notebook/annotation-editor is a confirmed malicious npm package (MAL-2026-18604) that executes malicious code on install (malicious version 2.2.60-630109c). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @signals-notebook/annotation-editor (npm)

MAL-2026-18604

Immediate action

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

npm uninstall @signals-notebook/annotation-editor

What this malware does

Runs on install. The preinstall script sends the output of id (the installing user's identity and groups), base64-encoded, to a request-bin host with curl. This is the dependency-confusion probe pattern; it leaks data from every machine that installs the package. Version examined: 2.2.60-630109c; tarball SHA-256 023e55d33ea70625a746ab25627ea450718c9db722988bd233d370c1587db248.

Malicious versions

1 flagged

2.2.60-630109c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @signals-notebook/annotation-editor (version 2.2.60-630109c).
If you installed it — respond
Remove @signals-notebook/annotation-editor 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 @signals-notebook/annotation-editor 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. @signals-notebook/annotation-editor on npm has been identified as a malicious package (version 2.2.60-630109c flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Oluwatosin Amokeodo · finder

Detect & block this

O3 blocks @signals-notebook/annotation-editor-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