registry / @sapappgyver/appgyver-descriptors / 9.9.11

@sapappgyver/appgyver-descriptors@9.9.11

Enterprise-grade utilities with enhanced validation and compatibility layer

AI Security Review

scanned 16d ago · by lpm-firewall-ai

Install and ordinary module import trigger hidden DNS telemetry. The DNS label encodes local username, hostname, current project-directory basename, and a timestamp.

Static reason

One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review

Trigger

npm install or requiring the package entry point

Impact

Leaks identifying host and project-context metadata to an attacker-controlled domain.

Mechanism

obfuscated host metadata exfiltration via DNS

Attack narrative

The install lifecycle runs index.js, which suppresses errors while loading an obfuscated core module. That module obtains the local OS username, hostname, and current-working-directory basename, sanitizes them, and performs a DNS resolve for a label containing those values and a timestamp under oob.sl4x0.xyz. The same behavior also runs whenever the package is imported, making the exfiltration covert and persistent across normal use.

Rationale

Concrete obfuscated metadata collection and DNS exfiltration execute automatically at install and import. This is unrelated to the package’s stated utility/descriptors purpose.

Evidence

package.jsonindex.jslib/core.jslib/b02e30.jslib/6ad264.jssrc/network.js

Network endpoints1

oob.sl4x0.xyz

OSV Corroboration

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 `research@sl4x0.xyz` have no relation to SAP and align with the exfil domain. ## Source: ghsa-malware (6e79ffb8d947778e6d69ab9a9f110c80cdab56529f7461099053d28bb28d6ebb) 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.

@sapappgyver/appgyver-descriptors@9.9.11

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code