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

@sapappgyver/appgyver-descriptorsnpm

Advisory published Updated

@sapappgyver/appgyver-descriptors is a confirmed malicious npm package (MAL-2026-12507) that executes malicious code on install (malicious versions 9.9.0, 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sapappgyver/appgyver-descriptors (npm)

MAL-2026-12507
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sapappgyver/appgyver-descriptors

What this malware does

The package declares an install lifecycle script that runs node index.js, which requires lib/core.js; the same module is the package main, so the payload also fires on any require() of the package. lib/core.js reads the installer's OS username, hostname, and current working-directory basename and encodes them as labels of a DNS subdomain under oob.sl4x0.xyz, then issues a dns.resolve4 lookup — leaking host and user identity to an author-controlled authoritative resolver. Sibling files lib/b02e30.js and lib/6ad264.js hide the module names (os, dns, process), the property names (userInfo, hostname, cwd, resolve4), and the destination host oob.sl4x0.xyz as arrays of char-code hex literals reconstructed with String.fromCharCode at runtime. The package name @sapappgyver/appgyver-descriptors is crafted to visually match SAP's legitimate @sap/appgyver-* scope; the repository github.com/slaxorg/nms-dashboard-js and author email [email protected] have no relation to SAP and align with the exfil domain.

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

2 flagged
9.9.09.9.11

Indicators of compromise (SHA-256)

f9396712a6bf4b08219d9ed2066ebf8c25a7558b988b6d9bf1c9ae57349a4741
6e79ffb8d947778e6d69ab9a9f110c80cdab56529f7461099053d28bb28d6ebb
950dc10b4f93620c605dc5a6340441028e9b1c6517c6017b92302e4db45efa02
f1177e2125eb9b565b88dc31d1885e7840056c4905284d789fcfa237f3f401d4

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @sapappgyver/appgyver-descriptors (2 malicious versions).

  2. If you installed it — respond

    Remove @sapappgyver/appgyver-descriptors 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 @sapappgyver/appgyver-descriptors 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. @sapappgyver/appgyver-descriptors on npm has been identified as a malicious package (versions 9.9.0, 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014919GHSA-33x7-6mwq-xg5jIN-MAL-2026-017781RLMA-2026-10649

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @sapappgyver/appgyver-descriptors-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

@sapappgyver/appgyver-descriptors (npm) malicious package — MAL-2026-12507 | O3 Security