@ibrahim1337/baksen
hadiyapic
This report shows the evidence for @ibrahim1337/baksen@3.0.0. 19 of 20 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe package’s primary behavior is browser credential harvesting/decryption, with obfuscation and a native debug-elevator addon increasing risk beyond ordinary package-aligned functionality. Lack of an install-time payload or exfil endpoint lowers certainty about automated theft, but the capability and import-time activation justify blocking.
Decision evidence
public snapshot- index.js import-time loads bytenode and executes ./index.jsc as package main
- cli.js describes itself as Chromium Cookie Extractor and forwards to index.js
- index.jsc contains obfuscated runtime logic for browser cookie/password extraction and decryption
- build/Release/debugelevator.node exports decryptCookie, decryptPassword, extractMasterKey, extractKey
- native binary imports CreateProcessW, WaitForDebugEvent, ReadProcessMemory, CryptUnprotectData, BCryptDecrypt
- src/license.jsc contacts https://raw.githubusercontent.com/tabo1337/SaatPCBKod/refs/heads/main/key.txt for license validation
- package.json install script is only echo and does not execute payload at install time
- No confirmed credential exfiltration endpoint found beyond the license-key URL
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage ships native binary artifacts.
build/Release/debugelevator.nodeView on unpkgFindings
Affected versions and remediation
This report applies to @ibrahim1337/baksen@3.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ibrahim1337/baksen@3.0.0. 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.