registry / Credential exfiltration / developer-dashboard
developer-dashboard
An awesome developer dashboard.
This report shows the evidence for developer-dashboard@1.0.3. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect source inspection confirms concrete credential/session theft and exfiltration behavior in index.js. The lack of lifecycle hooks limits automatic activation but does not negate the malicious payload.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Direct execution or import of index.js
Impact
Account takeover and disclosure of passwords, cookies, tokens, sessions, and host data.
Mechanism
obfuscated credential harvesting and webhook exfiltration
Attack narrative
Although not wired to an install hook, index.js immediately runs an obfuscated stealer. It gathers browser credentials and application sessions, packages selected data, captures a screenshot, and posts results to a hard-coded Discord webhook and external upload endpoints. The absent manifest entrypoint disguises the payload rather than making it benign.
AI rationale
Direct source inspection confirms concrete credential/session theft and exfiltration behavior in index.js. The lack of lifecycle hooks limits automatic activation but does not negate the malicious payload.
Evidence
index.jspackage.json
Network endpoints3
discord.comeconomy.roblox.comapi.steampowered.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js is a 438KB obfuscated credential-stealer payload.
- Immediate async IIFE executes collection when index.js runs.
- Collects browser cookies/passwords, Discord tokens, and Roblox/Instagram/Spotify sessions.
- Archives Steam, Minecraft, and Telegram session data for upload.
- Posts harvested data to a hard-coded Discord webhook and other external services.
- Disables TLS verification and uses shell commands for collection/screenshot capture.
Evidence against
- package.json has no preinstall/install/postinstall hook.
- Declared main/bin target app.js is absent; index.js is not the manifest entrypoint.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemShellWebSocket
HighEntropyStringsMinifiedObfuscatedProtestwareTrivialUrlStrings
Source & flagged code
9 flagged · loading sourceindex.jsView file
1const a0_0x5e6b0a=a0_0x2b7d;(function(_0x34c1ef,_0x887b13){const _0x5383f2=a0_0x2b7d,_0xf74132=_0x34c1ef();while(!![]){try{const _0x616dd2=parseInt(_0x5383f2(0x2d0))/0x1*(parseInt(...
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
index.jsView on unpkg · L11const a0_0x5e6b0a=a0_0x2b7d;(function(_0x34c1ef,_0x887b13){const _0x5383f2=a0_0x2b7d,_0xf74132=_0x34c1ef();while(!![]){try{const _0x616dd2=parseInt(_0x5383f2(0x2d0))/0x1*(parseInt(...
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
index.jsView on unpkg · L11const a0_0x5e6b0a=a0_0x2b7d;(function(_0x34c1ef,_0x887b13){const _0x5383f2=a0_0x2b7d,_0xf74132=_0x34c1ef();while(!![]){try{const _0x616dd2=parseInt(_0x5383f2(0x2d0))/0x1*(parseInt(...
High
Findings
2 Critical7 High4 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationindex.js
CriticalCredential Exfiltrationindex.js
HighChild Processindex.js
HighShellindex.js
HighSame File Env Network Executionindex.js
HighObfuscated Payload Loaderindex.js
HighObfuscated
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumDynamic Requireindex.js
MediumEnvironment Vars
MediumProtestware
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to developer-dashboard@1.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing developer-dashboard@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.