Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

mtslink-depconf-probe-profileusernamenpm

mtslink-depconf-probe-profileusername is a confirmed malicious npm package (MAL-2026-14137) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mtslink-depconf-probe-profileusername (npm)

MAL-2026-14137
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mtslink-depconf-probe-profileusername

What this malware does

Package ships an empty index.js and a preinstall lifecycle script that performs a DNS lookup against probe.4otph6fase1x2won0hrfzul2wt2qqge5.oastify.com (Burp Collaborator out-of-band infrastructure). On npm install, the installer's resolver contacts the attacker-controlled subdomain, leaking install-time telemetry (resolver IP, timing, and the unique subdomain identifier) to a third party. The package name pattern and description ('Bug bounty auth probe - safe empty package') indicate a dependency-confusion / typosquat probe targeting an internal namespace; the only functionality is the outbound beacon.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

f679922753b7a59c59af851ae74275b5d4760b13fc516bc8c68e8e9568393dc6

Detection & response playbook

Backdoor / remote access

  1. Find it

    Search your lockfiles and build artifacts for mtslink-depconf-probe-profileusername (version 1.0.0).

  2. If you installed it — respond

    mtslink-depconf-probe-profileusername establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If mtslink-depconf-probe-profileusername was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mtslink-depconf-probe-profileusername on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018175

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks mtslink-depconf-probe-profileusername-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
mtslink-depconf-probe-profileusername (npm) malicious package — MAL-2026-14137 | O3 Security