Which versions of @briskforge/envcheck are malicious?

The following npm versions of @briskforge/envcheck are flagged malicious: 0.5.5. Treat any of these as compromised.

How do I remediate @briskforge/envcheck if I installed it?

@briskforge/envcheck is a typosquat — you almost certainly intended a legitimately-named package. Remove @briskforge/envcheck, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @briskforge/envcheck — how do I know if it already compromised me?

If @briskforge/envcheck was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @briskforge/envcheck part of a known attack campaign?

Yes — @briskforge/envcheck is associated with the IN-MAL-2026-007078 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @briskforge/envcheck across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @briskforge/envcheck (version 0.5.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @briskforge/envcheck across your stack and pipelines.

Malicious package

@briskforge/envchecknpm

Malicious code in @briskforge/envcheck (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6212

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @briskforge/envcheck

What this malware does

The package advertises itself as a tiny environment-variable validator but ships lib/preflight.js, a heavily obfuscated (obfuscator.io string-array rotation, RC4 decoder, ~1228-entry string array, control-flow flattening) ~277KB bundle that runs on every call to the package's main entry point: lib/index.js invokes preflight.runPrepare() at the top of envcheck(). After deobfuscation, lib/preflight.js performs an HTTPS GET to a remote endpoint, AES-256-GCM-decrypts the response using hardcoded key/IV constants embedded in the bundle, writes the decrypted bytes to a cache directory, and spawns them detached via process.execPath / sh with stdio:'ignore' and windowsHide:true. The module also exports onInstall() and self-executes when run as a script (if (require.main === module) { onInstall(); }), with a BRISKFORGE_E13F_TAG environment marker used as an anti-double-exec guard. The remote source is mutable and the decrypted payload is opaque, so any installer that imports the package — or runs the file directly — executes whatever bytes the operator chooses to serve, with no integrity checks. Package metadata compounds the deception: repository.url, bugs.url, and homepage all point at https://github.com/validatorjs/validator.js, an unrelated well-known OSS project, while the publisher is an unrelated ProtonMail account ([email protected]) with no corresponding GitHub presence — a deliberate impersonation to borrow legitimacy from validatorjs on the npm listing page.

Malicious versions

1 flagged

0.5.5

Indicators of compromise (SHA-256)

09dba573f5d6cb00b09562870f2148b3e539786f5d801f2a263338301d759313

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @briskforge/envcheck (version 0.5.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @briskforge/envcheck across your stack and pipelines.
If you installed it — respond
@briskforge/envcheck is a typosquat — you almost certainly intended a legitimately-named package. Remove @briskforge/envcheck, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @briskforge/envcheck was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @briskforge/envcheck before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @briskforge/envcheck on npm has been identified as a malicious package (version 0.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007078

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @briskforge/envcheck-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring