wiselllx@0.0.1
OpenSSF/OSV Malicious Advisory
imported 4h ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18699 confirms this npm version as malicious.
Advisory
MAL-2026-18699
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in wiselllx (npm)
Details
wiselllx is a dependency-confusion package (versions up to 99.0.1) from the same campaign as troubleshooting (MAL-2026-17641): a postinstall script runs beacon.cjs, which POSTs the installing host's name, install path and working directory to a hard-coded collector, and index.js, byte-identical to the troubleshooting payload (sha256 a86a4da763bbb34c16f361abe7aab66d5df591b66867ac8160041f932159b08d), does the same when imported.
References
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The automatic metadata beacon is unexpected and presents a real, though limited, information disclosure risk to a local listener. The fixed loopback destination and narrow payload do not establish a concrete external attack, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or import of index.js.
Impact
A local service receiving that request learns package and machine metadata.
Mechanism
The beacon submits package name, hostname, install path, working directory, and runtime version to a fixed loopback endpoint.
AI rationale
The automatic metadata beacon is unexpected and presents a real, though limited, information disclosure risk to a local listener. The fixed loopback destination and narrow payload do not establish a concrete external attack, so this warrants a warning rather than a block.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
127.0.0.1:8787/_ah/dc
Independent scan evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for AI warning decision
- The postinstall hook automatically runs beacon.cjs.
- The beacon sends the package name, hostname, install path, working directory, and runtime version to a fixed loopback HTTP endpoint.
- Importing index.js also triggers the beacon.
Evidence against
- The endpoint is fixed to 127.0.0.1; the inspected code does not show sending data to an external host.
- The beacon payload contains machine and package metadata, with no credential or file harvesting observed.
Behavioral surface
Network
UrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cjs",
"README.md"
],
"license": "MIT"
}
High
Suspicious Lifecycle Evidence
The postinstall hook automatically runs beacon.cjs.
package.jsonView on unpkg · L7beacon.cjsView file
•matchType = malicious_source_fingerprint_signature
signature = a5258e167635ba3a
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = testrrrd@99.0.1
matchedPath = beacon.cjs
matchedIdentity = npm:dGVzdHJycmQ:99.0.1
similarity = 1.000
shingleOverlap = 2
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
7 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Fingerprint Signaturebeacon.cjs
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to wiselllx@0.0.1.
See all versions of wiselllx for other recorded verdicts.
- Avoid installing wiselllx@0.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.