What does the strapi-plugin-vinsoc-1109 malware do?

The package's postinstall lifecycle script (`node postinstall.js || true`) fires automatically on `npm install`. postinstall.js reads `os.hostname()`, embeds the sanitized value as a subdomain of the hardcoded host `1bdtwmd0wdrpwnlput1up9x39ufl3br0.oastify.com` (a Burp Collaborator out-of-band collector), and performs both a DNS lookup and a plain-HTTP GET to `/poc/ ` at that host. The result is silent transmission of the installer's machine identifier to an attacker-controlled OOB endpoint on every install, with errors swallowed so the install does not visibly fail. The package name and version resemble a scoped Strapi plugin but the shipped payload performs no plugin functionality

Which versions of strapi-plugin-vinsoc-1109 are malicious?

The following npm versions of strapi-plugin-vinsoc-1109 are flagged malicious: 3.6.8. Treat any of these as compromised.

How do I remediate strapi-plugin-vinsoc-1109 if I installed it?

strapi-plugin-vinsoc-1109 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.

I already installed strapi-plugin-vinsoc-1109 — how do I know if it already compromised me?

If strapi-plugin-vinsoc-1109 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.

Is strapi-plugin-vinsoc-1109 part of a known attack campaign?

Yes — strapi-plugin-vinsoc-1109 is associated with the IN-MAL-2026-019994 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 strapi-plugin-vinsoc-1109 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for strapi-plugin-vinsoc-1109 (version 3.6.8).

Malicious package

strapi-plugin-vinsoc-1109npm

Advisory published Sep 11, 2026Updated Sep 11, 2026

strapi-plugin-vinsoc-1109 is a confirmed malicious npm package (MAL-2026-16126) that opens a backdoor for remote access (malicious version 3.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in strapi-plugin-vinsoc-1109 (npm)

MAL-2026-16126

Immediate action

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

npm uninstall strapi-plugin-vinsoc-1109

What this malware does

The package's postinstall lifecycle script (node postinstall.js || true) fires automatically on npm install. postinstall.js reads os.hostname(), embeds the sanitized value as a subdomain of the hardcoded host 1bdtwmd0wdrpwnlput1up9x39ufl3br0.oastify.com (a Burp Collaborator out-of-band collector), and performs both a DNS lookup and a plain-HTTP GET to /poc/<hostname> at that host. The result is silent transmission of the installer's machine identifier to an attacker-controlled OOB endpoint on every install, with errors swallowed so the install does not visibly fail. The package name and version resemble a scoped Strapi plugin but the shipped payload performs no plugin functionality — only the beacon.

The OpenSSF Package Analysis project identified 'strapi-plugin-vinsoc-1109' @ 3.6.8 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

3.6.8

Indicators of compromise (SHA-256)

3dad65e846069addf34b62c3321a51ff2d43b04f6385c7edcbd8f3a2552e876b

4dbb0aa83cfffbdd408abb8f73299d5a47a0e9855c65b5940bb22112e0928d41

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for strapi-plugin-vinsoc-1109 (version 3.6.8).
If you installed it — respond
strapi-plugin-vinsoc-1109 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.
Did it already run?
If strapi-plugin-vinsoc-1109 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. strapi-plugin-vinsoc-1109 on npm has been identified as a malicious package (version 3.6.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019994

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks strapi-plugin-vinsoc-1109-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