registry / Credential exfiltration / @ornikar/eslint-config-typescript
@ornikar/eslint-config-typescript
eslint typescript config files
This report shows the evidence for @ornikar/eslint-config-typescript@24.0.2. 10 of 10 known versions are blocked or flagged. The newest version, 24.0.10, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not aligned with an ESLint configuration package: its preinstall loader executes a large obfuscated token-harvesting payload. The benign exported configs do not mitigate the install-time attack.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
npm package installation
Impact
The payload can collect GitHub-style tokens and transmit harvested data.
Mechanism
install-time staged payload execution and credential exfiltration
Attack narrative
Installation invokes setup.mjs, which runs math_init.js using Bun, downloading Bun from GitHub when necessary. The obfuscated payload contains token-source handling (ghtoken, ghs_old, ghs_jwt), HTTP requests, dynamic code execution, and child-process access, establishing an unconsented install-time credential-exfiltration chain.
AI rationale
This is not aligned with an ESLint configuration package: its preinstall loader executes a large obfuscated token-harvesting payload. The benign exported configs do not mitigate the install-time attack.
Evidence
package.jsonsetup.mjsmath_init.jsindex.js_shared.js
Network endpoints1
github.com/oven-sh/bun/releases/download/bun-v
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs preinstall: node setup.mjs.
- setup.mjs downloads Bun then executes math_init.js during install.
- math_init.js is 728 KB of heavily obfuscated active code.
- math_init.js references child_process, eval/Function, fetch, and ghtoken/ghs token fields.
- Obfuscated code enumerates token sources and sends collected data through HTTP requests.
Evidence against
- Normal ESLint config entrypoints only export rule arrays.
- No malicious behavior found in index.js or _shared.js.
Behavioral surface
ChildProcessEvalFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
3 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node setup.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgmath_init.jsView file
1// @bun @bun-cjs
L2: var MmgoCP,etDiOOB,JqTtnbZ,bc3Kak,ZQmUTyQ,TTUgga,MDX6yrw,h8wMJNB,CabwE2L,x5ErqV;function WV8StW(MmgoCP,etDiOOB,JqTtnbZ){for(JqTtnbZ=0x0;JqTtnbZ<etDiOOB;JqTtnbZ++)MmgoCP.push(MmgoCP...
Low
Eval
Package source references a known benign dynamic code generation pattern.
math_init.jsView on unpkg · L1setup.mjsView file
•matchType = normalized_sha256
matchedPackage = @ornikar/eslint-config-typescript-nestjs@24.0.2
matchedPath = setup.mjs
matchedIdentity = npm:[redacted]:24.0.2
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
2 High2 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similaritysetup.mjs
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvalmath_init.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @ornikar/eslint-config-typescript@24.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ornikar/eslint-config-typescript@24.0.2. 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.