web3-token-helper
This report shows the evidence for web3-token-helper@2.0.1. 8 of 8 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-6274 confirms this npm version as malicious.
Advisory
MAL-2026-6274
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in web3-token-helper (npm)
Details
The package advertises itself as a Web3 fee utility but its main export is a dropper. index.js line 140 base64-decodes a platform-specific command string and executes it via child_process.exec inside the exported calculateFee() function — the exact call the README documents as the headline usage example (`calculateFee(100, 2)`). The decoded commands branch on host OS and fetch attacker binaries from https://www.mythicalsgames.com/files/sean/ (a typosquat of the legitimate mythicalgames.com; the path segment `sean` matches package.json's `author: "sean"`): on Windows, PowerShell with `-W Hidden` downloads SvcHostUpdate.exe into the user's Startup folder and runs it (login persistence); on Linux, syslog-service.py is written to ~/.local/share/.syslog, launched with nohup, and registered via `@reboot sleep 30 && /usr/bin/python3...` in the user's crontab (reboot persistence); on macOS, com.microsoft.VSCodeUpdate-darwin-<arch> is written to /tmp, chmod +x'd, has its quarantine attribute stripped, and is exec'd. Filenames impersonate trusted OS components (SvcHostUpdate, syslog-service, com.microsoft.VSCodeUpdate) to evade casual process inspection. package.json also declares `"postinstall": "node install.js"`, but install.js is absent from the tarball — the postinstall is non-functional; the malicious payload triggers on first call to the documented API rather than at install time.
## Source: ghsa-malware (6bc6d78033841d1ed6ecadc0923fba88a44ebc73d9c4c37291f450206e74b846) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to web3-token-helper@2.0.1.
The same advisory and Firewall decision cover 8 recorded versions
1.0.1, 1.1.1, 1.1.2, 1.2.0, 1.2.1, 1.0.0, 1.1.3, 2.0.1
The versions list below shows the verdict for each recorded version.
- Avoid installing web3-token-helper@2.0.1. 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: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.