The vulnerability lies in the spmrc package, specifically within the set and config functions in index.js. The core of the issue is a prototype pollution flaw. The set function takes a key and a value to update a configuration object. It splits the key by dots to create a nested object structure. However, it doesn't sanitize the keys, allowing an attacker to use __proto__ as a key component. For instance, a key like __proto__.isAdmin would cause the code to add an isAdmin property to Object.prototype. Consequently, every object in the application would inherit this isAdmin property, potentially leading to privilege escalation or other unexpected behavior. The config function is also vulnerable because it serves as a wrapper for set, directly passing the malicious input to it. Since there is no patched version of spmrc, the recommended mitigation is to either cease using the package or to implement strict input validation on the keys passed to these functions, blocking any keys containing __proto__, constructor, or prototype.