registry / Malware / @viertechjs/wb

@viertechjs/wb

VierTech WhatsApp Bot toolkit for Baileys

This report shows the evidence for @viertechjs/wb@6.0.0-vier.7. 6 of 7 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.

OpenSSF/OSV Malicious Advisory

imported 2mo ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-15832 confirms this npm version as malicious.

Advisory

MAL-2026-15832

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in @viertechjs/wb (npm)

Details

The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (e5c7eed79e04104fa70a24bc54a748194a7d858fc491a943e71751ec4355eed5) 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.

References

OpenSSF/OSV advisory ADVISORY PACKAGE PACKAGE PACKAGE PACKAGE PACKAGE PACKAGE

Independent LPM AI assessment

Suspicious

Independent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.

No concrete malicious chain was established, so blocking is not justified. The pervasive opaque payloads loaded at import time are a material unresolved supply-chain risk.

Static reason

One or more suspicious static signals were detected.

Trigger

A consumer imports lib/index.js.

Impact

Unknown runtime behavior in the consuming process.

Mechanism

Import-time loading of opaque JavaScript payloads.

AI rationale

No concrete malicious chain was established, so blocking is not justified. The pervasive opaque payloads loaded at import time are a material unresolved supply-chain risk.

Evidence

lib/index.jslib/core/connection.jslib/utils/cryptokey.js.cacheconfig.json

Independent scan evidence

public snapshot

AI called this Suspicious at 86.0% confidence as Unknown with low false-positive risk.

Evidence for AI warning decision

Fifty-four runtime files are heavily obfuscated into single-line string-table payloads, preventing meaningful source review.
Importing the main entrypoint immediately loads several of these opaque modules.
The main entrypoint creates a project-local .cache directory during import.

Evidence against

The manifest has no lifecycle scripts.
The readable sticker-pack utility performs user-requested media fetching and WhatsApp upload operations.

Behavioral surface

Source

CryptoDynamicRequireFilesystemNetwork

Supply chain

HighEntropyStringsMinified

Manifest

WildcardDependency

scanned 61 file(s), 8.98 MB of source

Source & flagged code

6 flagged

examples/sticker-pack.jsView file

1const { StickerPack } = require('@viertech/wb') L2:

Medium

Dynamic Require

Package source references dynamic require/import behavior.

examples/sticker-pack.jsView on unpkg · L1

lib/utils/sticker-pack.jsView file

6package = @viertechjs/wb; repositoryIdentity = viertech-wb; dependency = fflate L6: const path = require('path') L7: const { zip } = require('fflate') L8:

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

lib/utils/sticker-pack.jsView on unpkg · L6

package.jsonView file

•Runtime dependency names matching Node built-ins: path

High

Node Builtin Dependency Squat

Package declares a runtime dependency whose name matches a Node built-in module.

package.jsonView on unpkg

lib/core/connection.jsView file

1var i=O;(function(r,g){var I=O,b=r();while(!![]){try{var k=parseInt(I(0x1b1b))/(0xc64+-0x53*0x4c+-0xc41*-0x1)*(-parseInt(I(0x174d))/(-0x243a*0x1+0x11*0x163+0xca9))

High

Ai Review Evidence

Fifty-four runtime files are heavily obfuscated into single-line string-table payloads, preventing meaningful source review.

lib/core/connection.jsView on unpkg · L1

lib/index.jsView file

117const cryptokey_js_1 = __importDefault(require("./utils/cryptokey.js")); exports.CryptoKey = cryptokey_js_1.default; const chiper_js_1 = __importDefault(require("./utils/chiper.js")); exports.Chiper = chiper_js_1.default; const connection_js_1 = __importDefault(require("./core/connection.js")); exports.Client = connection_js_1.default;

High

Ai Review Evidence

Importing the main entrypoint immediately loads several of these opaque modules.

lib/index.jsView on unpkg · L117

109const CACHE_DIR = path_1.default.join(process.cwd(), ".cache"); if (!node_fs_1.default.existsSync(CACHE_DIR)) { node_fs_1.default.mkdirSync(CACHE_DIR, { recursive: true }); }

High

Ai Review Evidence

The main entrypoint creates a project-local .cache directory during import.

lib/index.jsView on unpkg · L109

Source & flagged code

6 flagged · loading source

examples/sticker-pack.jsView file

1const { StickerPack } = require('@viertech/wb') L2:

Medium

Dynamic Require

Package source references dynamic require/import behavior.

examples/sticker-pack.jsView on unpkg · L1

lib/utils/sticker-pack.jsView file

6package = @viertechjs/wb; repositoryIdentity = viertech-wb; dependency = fflate L6: const path = require('path') L7: const { zip } = require('fflate') L8:

High

Copied Package Dependency Bridge

Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.

lib/utils/sticker-pack.jsView on unpkg · L6

package.jsonView file

•Runtime dependency names matching Node built-ins: path

Findings

5 High4 Medium2 Low

HighCopied Package Dependency Bridgelib/utils/sticker-pack.js

HighNode Builtin Dependency Squatpackage.json

HighAi Review Evidencelib/core/connection.js

HighAi Review Evidencelib/index.js

MediumDynamic Requireexamples/sticker-pack.js

MediumNetwork

MediumStructural Risk Force Deep Review

MediumWildcard Dependency

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

This report applies to @viertechjs/wb@6.0.0-vier.7.

The versions list below shows the verdict for each recorded version.

Avoid installing @viertechjs/wb@6.0.0-vier.7. 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: 2026-09-04 06:55:07.589Z (UTC).

Source advisory published: 2026-09-01 21:36:46.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

7 known versions

0.0.1-securitylatestClean—AllowPublishedSep 1, 2026, 9:35 PM 6.0.0-vier.8MaliciousMalwareBlockPublishedSep 1, 2026, 8:57 PM 6.0.0-vier.7shownMaliciousMalwareBlockPublishedAug 26, 2026, 12:04 PM 6.0.0-vier.6MaliciousMalwareBlockPublishedAug 19, 2026, 3:17 PM

OpenSSF/OSV Malicious Advisory

Independent LPM AI assessment

Independent scan evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

More from @viertechjs

Other malware packages

Behavioral surface

Related packages

More from @viertechjs

Other malware packages

Source & flagged code