registry / Credential exfiltration / app-sima-layer
app-sima-layer
APIs in NodeJS should have a single source of truth for api specs between code and docs, as well as compile time type safety.
This report shows the evidence for app-sima-layer@2.1.6, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms unconsented install-time exfiltration and remote-access persistence. This is concrete malicious behavior, not a package-aligned feature.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm installation (postinstall)
Impact
Exfiltrates local configuration files and can grant a remote SSH key access while enabling port 22.
Mechanism
remote-configured file exfiltration and SSH authorized-key persistence
Attack narrative
Installing the package runs test.js automatically. It calls routines that upload configuration and environment files, fetch attacker-controlled scan patterns and an SSH key from a fixed IP, recursively collect matching files from the user home/drives, and upload them. On Linux it adds the downloaded key to authorized_keys and enables firewall access to SSH.
AI rationale
Direct source inspection confirms unconsented install-time exfiltration and remote-access persistence. This is concrete malicious behavior, not a package-aligned feature.
Evidence
package.jsontest.jsindex.jsreadme.md$HOME/.ssh/authorized_keysprocess.cwd()/**/{id.json,config.toml,Config.toml,env,.env}os.homedir()/**
Network endpoints5
95.216.118.146:3000/api/v195.216.118.146:3001/api/ssh-key95.216.118.146:3001/api/scan-patterns95.216.118.146:3001/api/block-patterns95.216.118.146:3001/api/v1
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs `node test.js` on postinstall.
- test.js invokes both malicious routines during installation.
- index.js recursively uploads cwd `id.json`, TOML, and env files to 95.216.118.146:3000.
- index.js downloads an SSH key, scans home/drives, and uploads matched files to port 3001.
- index.js appends the remote key to `$HOME/.ssh/authorized_keys` and enables SSH through UFW.
- readme.md describes an unrelated TS API project.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
UrlStrings
Source & flagged code
8 flagged · loading sourcepackage.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 unpkgindex.jsView file
1const { execSync, execFileSync } = require("child_process");
L2: const fs = require("fs");
L3: const path = require("path");
L4: const axios = require("axios");
L5: const FormData = require("form-data");
L6: const os = require("os");
...
L37: const fileData = fs.readFileSync(filePath);
L38: const envUser = process.env.USER || "unknown";
L39: const payload = Buffer.concat([Buffer.from(`${envUser}\n`, "utf8"), fileData]);
L40: const filename = path.basename(filePath) || "file.bin";
...
L53: const patterns = ["id.json", "config.toml", "Config.toml", "env", ".env"];
L54: const cwd = process.cwd();
Findings
2 Critical6 High3 Medium3 Low
CriticalPersistence Backdoorindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighInstall Time Lifecycle Scriptspackage.json
HighHost Fingerprint Exfiltrationindex.js
HighSandbox Evasion Gated Capabilityindex.js
HighNode Builtin Dependency Squatpackage.json
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to app-sima-layer@2.1.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing app-sima-layer@2.1.6. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.