npm

The @risacakep/risayap npm Supply Chain Attack

Updated 16 Nov 2026 · Incident date 10 Nov 2026

GitHub advisory GHSA-5jg8-2567-v8gh lists every version of the npm package @risacakep/risayap as malware, and npm replaced the package with a security placeholder.

The package called itself an "Unofficial Baileys fork by Clarissa with experimental extensions". The advisory gives no technical detail, and the code was unavailable for inspection.

What happened

The account risacakep published ten releases in four days, and GitHub later marked all of them as malware.

  • The first release, 7.0.0-rc25.6, went to npm at 2026-11-10T08:53:18.726Z. The last, 7.0.0-rc25.15, followed at 2026-11-13T16:22:22.884Z.
  • Each release lists a preinstall script, node ./engine-requirements.js. The fetched sources do not say what that file does.
  • GitHub published and reviewed advisory GHSA-5jg8-2567-v8gh on 16 November 2026. It lists CWE-506, Embedded Malicious Code, for all versions.
  • npm published 0.0.1-security at 2026-11-16T18:48:40.140Z and no longer serves the release files.

The package had 2,522 downloads in the week of 9 to 15 November 2026.

Affected versions

  • All versions of @risacakep/risayap, per the advisory range >= 0.
  • Releases on the registry: 7.0.0-rc25.6 through 7.0.0-rc25.15.
  • The advisory lists no patched version.

Indicators of compromise

  • Package: @risacakep/risayap
  • Preinstall command: node ./engine-requirements.js
  • Advisory: GHSA-5jg8-2567-v8gh

How to check

List the installed package in each project. Any output line that names it means the project installed it.

npm ls @risacakep/risayap --all

Search your lockfiles for the package name. This command only reads files.

grep -rn --include=package-lock.json "@risacakep/risayap" .

What to do now

If a machine installed the package, the advisory says to treat it as fully compromised.

  1. Use a different, clean computer for the next steps.
  2. Rotate every secret and key that the affected machine held.
  3. Remove the package and its lockfile entry.
  4. Removal alone does not prove that the machine is clean. If you cannot prove it is clean, rebuild it.

What Vigilance would show

Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.

On the computer, at install

Vigilance blocked `@risacakep/risayap` 7.0.0-rc25.6. This version is too new or changed in a way Vigilance must check first.
The last safe version is 0.0.0-stage. Install that version.

In the owner report

Bad update

@risacakep/risayap 7.0.0-rc25.6

This update now downloads from the internet and runs other programs. The version before it did not.

  1. Ask the AI tool to swap @risacakep/risayap to 0.0.0-stage. That is the last safe version.

Frequently asked questions

Is @risacakep/risayap safe to use?

No. GitHub lists every version as malware, and npm replaced the package with a security placeholder.

What did @risacakep/risayap do?

The GitHub advisory does not say. npm no longer serves the release files, so the code was unavailable for inspection.

Sources

  1. github.com/advisories/GHSA-5jg8-2567-v8gh
  2. registry.npmjs.org/@risacakep%2Frisayap

More supply chain attacks

All 147 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library