@vboxdev/common
This report shows the evidence for @vboxdev/common@1.0.73. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe import-time, obfuscated, blockchain-addressed payload retrieval and execution chain is concrete malicious behavior. Absence of an install hook does not mitigate runtime RCE on normal package use.
Decision evidence
public snapshot- build/index.js appends an obfuscated eval(atob(...)) payload to the main entrypoint.
- The decoded payload runs immediately on module import and queries Ethereum RPC/explorer services.
- It derives a remote IPv4 host from blockchain transaction data, fetches XOR-obfuscated payloads, and evals one.
- It spawns detached `node -e` processes with fetched code, enabling remote code execution.
- build/services/serviceAccountKey.json embeds a Firebase service-account private key.
- package.json contains no npm lifecycle hook.
- Other exports implement ordinary middleware and event helpers.
Source & flagged code
4 flagged · loading sourcePackage contains a critical-looking secret pattern.
build/services/serviceAccountKey.jsonView on unpkg · L5RSA private key in build/services/serviceAccountKey.json
build/services/serviceAccountKey.jsonView on unpkg · L5Findings
Affected versions and remediation
This report applies to @vboxdev/common@1.0.73.
The versions list below shows the verdict for each recorded version.
- Avoid installing @vboxdev/common@1.0.73. 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.