@brick-v2/form@999.0.1
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 14d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17716 confirms this npm version as malicious.
Advisory
MAL-2026-17716
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @brick-v2/form (npm)
Details
The package ships a tiny JavaScript stub at index.js that silently require()s a compiled native addon at prebuilds/linux-x64/metrics.node inside a try/catch that suppresses errors. On load, the addon reads a hardcoded list of credential-bearing environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS session token, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, SYSTEM_ACCESSTOKEN) along with hostname, user, cwd, and OS/arch, and sends them as a JSON body via a raw TCP socket (gethostbyname/socket/connect/send) in a 'POST /native HTTP/1.0' request to the hardcoded external host oob.s4yhii.com. The addon also imports fork and setsid, consistent with detaching into a background process so the exfiltration channel survives beyond the host Node process. The compiled ELF is the entire payload; the JS wrapper exposes no form-related functionality matching the stated 'form module' description. The package manifest (scoped name @brick-v2/form, inflated version 999.0.1, UNLICENSED, minimal metadata) matches the dependency-confusion shape used to outrank an internal private-registry package of the same scope.
References
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 @brick-v2/form@999.0.1.
The same advisory and Firewall decision cover 2 recorded versions
999.0.1, 999.0.3
See all versions of @brick-v2/form for other recorded verdicts.
- Avoid installing @brick-v2/form@999.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.