registry / app-data-layer / 2.1.6

app-data-layer@2.1.6

AI Security Review

scanned 10d ago · by lpm-firewall-ai

No confirmed malicious attack surface. The install hook executes test.js, which only self-imports and calls absent exports inside a catch block.

Static reason

One or more suspicious static signals were detected.

Trigger

npm postinstall

Impact

At most a caught runtime error written to stderr; no file, network, or process action is present.

Mechanism

Nonfunctional self-require and caught function calls

Rationale

Direct inspection found a broken postinstall hook but no concrete harmful behavior. Dependency names and lifecycle presence are insufficient to establish malicious intent.

Evidence

package.jsontest.jsreadme.md

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-11052

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in app-data-layer (npm)

Details

Analysis of app-data-layer@2.1.6 (3 files scanned) produced no static or traced findings. No lifecycle hooks fetching or executing remote content, no credential or environment reads, no hardcoded exfiltration destinations, and no obfuscated payloads were observed in the package contents. ## Source: ghsa-malware (4b8c073af489e9e7102ec43ca525f91f88615b572d4d0b0e65c6b64b647f93ae) 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.

References

OSV advisory ADVISORY PACKAGE

Decision evidence

public snapshot

AI called this Clean at 97.0% confidence as Benign with low false-positive risk.

Evidence for block

package.json defines postinstall: node test.js.
package.json lists child_process and os dependencies, but no package source imports them.

Evidence against

test.js is the only executable source and contains no network, filesystem, shell, eval, or environment access.
During postinstall, test.js self-requires the package, obtains no declared exports, and catches the resulting call error.
No source contains credential collection, payload download, persistence, or destructive operations.

Behavioral surface

SourceNo risky source behavior triggered.

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 269 B of source

Source & flagged code

2 flagged

package.jsonView file

•scripts.postinstall = node test.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•Runtime dependency names matching Node built-ins: child_process, os

High

Node Builtin Dependency Squat

Package declares a runtime dependency whose name matches a Node built-in module.

package.jsonView on unpkg

Source & flagged code

2 flagged · loading source

package.jsonView file

•scripts.postinstall = node test.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•Runtime dependency names matching Node built-ins: child_process, os

High

Node Builtin Dependency Squat

Package declares a runtime dependency whose name matches a Node built-in module.

package.jsonView on unpkg

Findings

2 High1 Low

HighInstall Time Lifecycle Scriptspackage.json

HighNode Builtin Dependency Squatpackage.json

LowScripts Present