registry / Credential exfiltration / @servicetitan/hammer-react
@servicetitan/hammer-react
This report shows the evidence for @servicetitan/hammer-react@1.42.5. 7 of 7 known versions are blocked or flagged. The newest version, 1.42.8, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe lifecycle hook is unrelated to a React UI library and deliberately stages an obfuscated payload. Direct source inspection confirms credential collection and remote content evaluation.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
npm preinstall during package installation
Impact
Possible theft of npm/GitHub credentials and arbitrary code execution under the installing user's privileges.
Mechanism
Bun-assisted execution of obfuscated credential stealer with remote eval
Attack narrative
The preinstall hook runs setup.mjs, which uses an installed Bun or downloads a Bun binary from GitHub and executes math_init.js. That obfuscated payload contains npm/GitHub token handling, process execution, network requests, and eval of remotely returned content; this is a concrete install-time credential-stealing remote-code-execution chain.
AI rationale
The lifecycle hook is unrelated to a React UI library and deliberately stages an obfuscated payload. Direct source inspection confirms credential collection and remote content evaluation.
Evidence
package.jsonsetup.mjsmath_init.js
Network endpoints1
github.com/oven-sh/bun/releases/download/bun-v1.3.13/
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs `node setup.mjs` as preinstall.
- setup.mjs executes obfuscated math_init.js, downloading Bun from github.com if absent.
- math_init.js contains credential-token handling for npm and GitHub token types.
- math_init.js fetches a response body and executes its `content` with eval.
- math_init.js imports child_process and contains credential collection/exfiltration workflow.
Evidence against
- dist/ contains the expected React component build, but is not the preinstall path.
- The only clear setup.mjs network host is Bun's GitHub release, used to launch the hidden payload.
Behavioral surface
ChildProcessEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
NoLicense
Source & flagged code
4 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
1Manifest entrypoint (scripts.preinstall) carries capability families absent from dist/build output: execution+network
L1: #!/usr/bin/env node
L2: import { execFileSync } from "child_process";
L3: import _0x488df8 from "fs";
L4: import _0x52943e from "https";
L5: import _0x24db8d from "os";
...
L50: function ra() {
L51: const _0x51cd53 = process.platform + "-" + process.arch;
L52: const _0x3ab5c4 = PM[_0x51cd53];
...
L218: } else if (_0xc0d7d2 === 8) {
L219: _0x27994e = _0x548d91.inflateRawSync(_0x5975df);
L220: } else {
Findings
3 High3 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighEntrypoint Build Divergencesetup.mjs
HighKnown Malware Source Similaritysetup.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvalmath_init.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @servicetitan/hammer-react@1.42.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @servicetitan/hammer-react@1.42.5. 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.