registry / randompkga / 1.0.20

randompkga@1.0.20

AI Security Review

scanned 15d ago · by lpm-firewall-ai

No confirmed attack surface. The only install hook invokes echo; the text resembling a crontab write is commented out by the shell.

Static reason

One or more suspicious static signals were detected.

Trigger

npm postinstall

Impact

No confirmed file mutation or execution beyond echo.

Mechanism

harmless echo command with commented trailing text

AI rationale

Direct source inspection found no executable malicious behavior. The scanner hit is a shell-comment false positive.

Evidence

package.json

OSV advisory

OpenSSF/OSV

Advisory

MAL-2026-16255

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in randompkga (npm)

Details

package.json declares a postinstall lifecycle script `cd "$INIT_CWD" && npm i randompkgb` that, on `npm install`, installs the additional npm package `randompkgb` into the consumer's project. A companion postinstall.js reads the installer's own package.json at $INIT_CWD, sets `dependencies.randompkgb = "^1.0.0"`, and writes the manifest back to disk, persisting the injected dependency across future installs and CI runs. The caret range is unpinned, so any current or future version of `randompkgb` — whose code is not present in this package and is not controlled by the installer — will be resolved and executed on the installer's machine at install time and on `require`. This is dependency-tree hijacking: the mechanism drops attacker-controlled third-party code into the installer's environment and rewrites source-controlled project state to make the injection durable. ## Source: ghsa-malware (cfdfcd7cd3af1c7b280e6f13503a472f2b31582e239d6fac0b6cacc1709cf36f) 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 PACKAGE PACKAGE

Decision evidence

public snapshot

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

Evidence for AI clean decision

The sole lifecycle hook is postinstall, but its apparent crontab redirect follows a shell comment marker and is not executed.
Package contains only package.json; the declared index.js entrypoint is absent.

Evidence against

No network, credential, file-harvesting, child-process, dynamic-code, persistence, or destructive source is present.
The active postinstall command reduces to a harmless echo.

Behavioral surface

SourceNo risky source behavior triggered.

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 0 file(s), 0 B of source

Source & flagged code

2 flagged

package.jsonView file

•scripts.postinstall = echo # 1 >> /etc/crontab

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "postinstall": "echo # 1 >> /etc/crontab" }

High

Suspicious Lifecycle Evidence

The sole lifecycle hook is postinstall, but its apparent crontab redirect follows a shell comment marker and is not executed.

package.jsonView on unpkg · L6

Source & flagged code

2 flagged · loading source

package.jsonView file

•scripts.postinstall = echo # 1 >> /etc/crontab

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "postinstall": "echo # 1 >> /etc/crontab" }

High

Suspicious Lifecycle Evidence

The sole lifecycle hook is postinstall, but its apparent crontab redirect follows a shell comment marker and is not executed.

package.jsonView on unpkg · L6

Findings

2 High1 Low

HighInstall Time Lifecycle Scriptspackage.json

HighSuspicious Lifecycle Evidencepackage.json

LowScripts Present

Affected versions and remediation

This report applies to randompkga@1.0.20.

See version security history for other recorded verdicts.

Avoid installing randompkga@1.0.20. 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-09-23 04:40:08.444Z (UTC).

Source advisory published: 2026-09-17 14:59:20.000Z (UTC).