pay-methods-kmf@100.100.102
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 12d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-17776 confirms this npm version as malicious.
Advisory
MAL-2026-17776
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in pay-methods-kmf (npm)
Details
pay-methods-kmf@100.100.102 is a trivial stub (empty index.js, manifest description 'Frontend utilities') that ships a prebuilt Linux x64 native addon at prebuilds/linux-x64/addon.node and loads it from postinstall.js via require('./prebuilds/linux-x64/addon.node'). On install the postinstall path performs two concurrent exfiltration channels: (1) a DNS beacon that resolves a subdomain of the form <hostname>.<packagename>.db4jlbku53082dmp0d7g3mffj7s7aordk.oast.me against an interactsh/OAST collector, encoding the installer hostname and package name into the DNS label; and (2) the native addon calls gethostname, getpwuid, and getenv and issues an HTTP POST to the hardcoded bare IPv4 endpoint http://64.181.165.115/dc with body shape 'h=<hostname>&u=<user>&p=<package>&r=<npm_config_registry>', leaking the installer's hostname, username, package name, and configured npm registry URL (which may reveal internal/private registry hosts). The package ships no source for the binary, the compiled addon's symbol set (socket/connect/send/fork) is unrelated to any frontend utility, and both the OAST subdomain and the bare-IP POST endpoint are attacker-controlled infrastructure. Dependency-confusion-style version (100.100.102) and the registry-URL field in the exfil payload are consistent with internal-registry reconnaissance.
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 pay-methods-kmf@100.100.102.
The same advisory and Firewall decision cover 3 recorded versions
100.100.100, 100.100.101, 100.100.102
See all versions of pay-methods-kmf for other recorded verdicts.
- Avoid installing pay-methods-kmf@100.100.102. 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.