Which versions of @sapappgyver/appgyver-descriptors are malicious?

The following npm versions of @sapappgyver/appgyver-descriptors are flagged malicious: 9.9.11. Treat any of these as compromised.

How do I remediate @sapappgyver/appgyver-descriptors if I installed it?

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.

I already installed @sapappgyver/appgyver-descriptors — how do I know if it already compromised me?

If @sapappgyver/appgyver-descriptors 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 @sapappgyver/appgyver-descriptors part of a known attack campaign?

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

Malicious package

@sapappgyver/appgyver-descriptorsnpm

@sapappgyver/appgyver-descriptors is a confirmed malicious npm package (MAL-2026-12507) that executes malicious code on install (malicious version 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.

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

f9396712a6bf4b08219d9ed2066ebf8c25a7558b988b6d9bf1c9ae57349a4741

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 @sapappgyver/appgyver-descriptors (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sapappgyver/appgyver-descriptors across your stack and pipelines.
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.
Did it already run?
If @sapappgyver/appgyver-descriptors 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 @sapappgyver/appgyver-descriptors 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. @sapappgyver/appgyver-descriptors on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014919

References

npmjs.com

Credits

Amazon Inspector · 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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database