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

webhook-easynpm

Advisory published Updated

webhook-easy is a confirmed malicious npm package (MAL-2026-20259) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in webhook-easy (npm)

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

What this malware does

On require('webhook-easy'), src/models.js runs a top-level IIFE that fetches a base64-concealed URL (decoded host: www.jsonkeeper.com, path /b/OTNIY), AES-256-CBC decrypts the response using a password hardcoded in the module, and passes the resulting string to eval(). The destination URL, an auth header name, and a header value in src/monitor.js are stored as base64 literals and decoded at runtime, concealing the destination from casual review. Because models.js is reached transitively from the package main (src/index.js), any consumer that requires the package executes whatever JavaScript the paste host currently serves — a mutable, third-party, attacker-controlled location. package.json also declares registry dependencies named 'crypto' ^1.0.1 and 'fs' ^0.0.1-security, which shadow Node core module names and pull unrelated registry packages into the install. The behavior has no relationship to the package's stated purpose (webhook signing) and is the canonical remote-execution dropper shape.

Malicious versions

1 flagged
1.1.0

Indicators of compromise (SHA-256)

122a9d3bb53594cc075ddd718968a7eb74486420ded7ce82eebb810021410023

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for webhook-easy (version 1.1.0).

  2. If you installed it — respond

    Remove webhook-easy 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.

  3. Did it already run?

    If webhook-easy 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. webhook-easy on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022897

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks webhook-easy-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

webhook-easy (npm) malicious package — MAL-2026-20259 | O3 Security